Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 303010 - kde-base/dolphin-4.3.3 : random crashes mostly when Back button is pressed
Summary: kde-base/dolphin-4.3.3 : random crashes mostly when Back button is pressed
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-31 18:48 UTC by Juraj Variny
Modified: 2010-02-02 09:30 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
KDE Crash handler report (dolphin-20100131.kcrash,2.20 KB, text/plain)
2010-01-31 18:51 UTC, Juraj Variny
Details
emerge --info output (emerge-info.txt,4.43 KB, text/plain)
2010-01-31 18:53 UTC, Juraj Variny
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Juraj Variny 2010-01-31 18:48:08 UTC
After starting instance of Dolphin, it crashes after several seconds or minutes. Most often after clicking on Back button.

Reproducible: Sometimes

Steps to Reproduce:
Did not find exact way to reproduce.

Actual Results:  
Dolphin window disappears and KDE Crash handler appears.

Expected Results:  
Obvious

Executable: dolphin PID: 28989 Signal: 11 (Segmentation fault)
Comment 1 Juraj Variny 2010-01-31 18:51:12 UTC
Created attachment 218005 [details]
KDE Crash handler report
Comment 2 Juraj Variny 2010-01-31 18:53:46 UTC
Created attachment 218006 [details]
emerge --info output
Comment 3 Viktor S 2010-02-01 11:21:50 UTC
Please report this upstream (https://bugs.kde.org) since they're the ones most probable to need to know about this. Put the URL of the bug on the KDE Bugzilla in the URL-field above. Thanks!
Comment 4 Juraj Variny 2010-02-01 16:13:09 UTC
Seems to be resolved by upstream.
Comment 5 Viktor S 2010-02-01 18:44:28 UTC
Then please close this as UPSTREAM and wait for 4.3.5 to be stabled (bug #300393)