Bug 262407

Summary:	Crash on ejecting an USB stick
Product:	[Applications] dolphin	Reporter:	Silviu Marin-Caea <silviumc>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	frank78ac, kollix
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Silviu Marin-Caea 2011-01-07 13:46:55 UTC

Application: dolphin (1.5.9)
KDE Platform Version: 4.5.85 (4.6 Beta2)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-rc7-desktop x86_64
Distribution: "openSUSE 11.4 Milestone 5 of 6 (x86_64)"

-- Information about the crash:
Dolphin crashes all the time.  The bug reporting process is annoying.  It should do all the work automatically, generating backtraces and such.  Then is should send data to be aggregated into STATISTICS.  And you'd see what are the most frequent causes for crashes.

Not open a frigging new bug for every crash.  Not asking the user to identify duplicates.  This sucks donkey dick.

 Ask Mozilla for a lesson, they can teach you about "talkback assistant".  That's how it all should work.

Now you have thousands of bugs opened.  What good does it do for you?

I was nasty and criticised your voluteer work.  That wasn't fair.  But this is what a crashing file manager does to people!  It's the file manager, one of the most used applications.

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Aborted
[KCrash Handler]
#6  0x00007f79c3762a75 in raise () from /lib64/libc.so.6
#7  0x00007f79c3763f76 in abort () from /lib64/libc.so.6
#8  0x00007f79c379dcc3 in __libc_message () from /lib64/libc.so.6
#9  0x00007f79c37a32a6 in malloc_printerr () from /lib64/libc.so.6
#10 0x00007f79c3b3d2d9 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib64/libstdc++.so.6
#11 0x00007f79c3765581 in __run_exit_handlers () from /lib64/libc.so.6
#12 0x00007f79c37655d5 in exit () from /lib64/libc.so.6
#13 0x0000000000407600 in _start ()

This bug may be a duplicate of or related to bug 262404.

Possible duplicates by query: bug 262404, bug 262365, bug 262354, bug 262345, bug 262299.

Reported using DrKonqi

Comment 1 Martin Koller 2011-01-07 23:20:55 UTC


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

Comment 2 Frank Reininghaus 2011-01-08 12:40:36 UTC

Thanks for your report. For some information why Mozilla's crash reporting system would *not* work for KDE, please read the thread

http://lists.kde.org/?t=129173966500006&r=1&w=2 (click on "Next" to see the first mail in the thread).

If you don't like the way the bug reporting process works, feel free to get involved and help to improve it. Your contributions will be more than welcome!

Comment 3 Silviu Marin-Caea 2011-01-09 19:24:36 UTC

I'm very sorry about the rude rant.  My sincere apologies.

Fact remains that the bug reporting process for crashing KDE apps requires more than a bit of user effort.  It is beyond what a regular user is willing to make.

I promise that I, myself, am going to make this effort to make up for my bitching in this bug report.

Thanks for not taking the bait and replying politely with useful information.