Bug 187931 - A Fatal Error Occurred The application Dolphin (dolphin) crashed and caused the signal 11 (SIGSEGV).
Summary: A Fatal Error Occurred The application Dolphin (dolphin) crashed and caused t...
Status: RESOLVED DUPLICATE of bug 173054
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-23 16:55 UTC by malavoie
Modified: 2009-04-30 12:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Dolphin Crash Report (5.14 KB, application/octet-stream)
2009-03-27 03:12 UTC, chrismuellner 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description malavoie 2009-03-23 16:55:09 UTC 
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Compiled From Sources

Doen't create major problem, datas and revision are kept narmally.
Comment 1 Frank Reininghaus 2009-03-23 20:57:12 UTC 
Thanks for the bug report. Could you describe what you did before the crash so that we can try to reproduce the problem? A backtrace might also help, see

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 chrismuellner 2009-03-27 03:12:01 UTC 
Created attachment 32423 [details]
Dolphin Crash Report
Comment 3 chrismuellner 2009-03-27 03:14:01 UTC 
Comment for my attachment: Had two Dolphin windows open (KDE4.1.4) - one was connected to an smb:// share and the other windows was to a local folder. I was copying files from one window (smb://) to the other, but the process had finished before the crash occurred.
Comment 4 Frank Reininghaus 2009-03-28 22:30:32 UTC 
comment 2, 3: Your crash is probably fixed in KDE 4.2.0 (see bug 173054). If you can reproduce it in 4.2.0 or later, please install debugging packages to get a more detailed backtrace and file a new report. Thanks!
Comment 5 Peter Penz 2009-04-30 12:18:30 UTC 

*** This bug has been marked as a duplicate of bug 173054 ***