abrt detected a crash. How to reproduce ----- 1. 2. 3. Comment ----- I was surfing a site with flash when abrt popped up with this. I don't know if it is a nspluginwrapper issue of if nspluginwrapper could do anything to prevent it. If nspluginwrapper don't care about this flash crash then abrt shouldn't have assigned it to nspluginwrapper. Additional information ====== Attached files ---- backtrace cmdline ----- /usr/lib/nspluginwrapper/npviewer.bin --plugin /usr/lib/mozilla/plugins/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/1653-1 component ----- nspluginwrapper executable ----- /usr/lib/nspluginwrapper/npviewer.bin kernel ----- 2.6.31-0.199.rc8.git2.fc12.i686.PAE package ----- nspluginwrapper-1.3.0-8.fc12 reason ----- Process was terminated by signal 11
Created attachment 359921 [details] File: backtrace
Hm, it looks like a crash somewhere in GTK...not the flash one.
Nope. This is a crash in gconf-editor. Since the stacktrace has no relation to the description in the bug, I am going to close this. Or wait. I'll actually move it to abrt, so we can fix the problem of bugs with unrelated stacktraces...
Right. I don't know how that happened. That stacktrace belongs on bug 521507 where it was filed. nsnpluginwrapper crash was in /var/cache/abrt/ccpp-1252197179-13854 gconf-editor crash was in /var/cache/abrt/ccpp-1252250554-1742 I think I had abrt-0.0.8.5-1.fc12.i686 installed at that time.
Created attachment 360363 [details] /var/cache/abrt/ccpp-1252197179-13854/backtrace from nspluginwrapper This issues has been reassigned and moved around, but just in case anybody cares I have attached the nspluginwrapper stacktrace which should have been attached in the first place.
Hi, it seems that abrtdb is messed up, could you please send me the whole /var/cache/abrt/ dir? Thank you, Jirka
Ok, please run abrt in the debug mode $ abrtd -dvvv and try to report this bug again. Then copy and paste the output. Thanks.
abrt-gui just tells me that it has been submitted here and does not allow me to report it again. How can I make it forget that report?
Another question. I suppose that you have also Logger reporter enabled. So take a look into file /var/log/abrt and try to find this report (search for uuid [see whiteboard]). Is it also corrupted? If not, that the bug isn't in abrt itself but in bz plugin. Thanks.
(In reply to comment #8) > abrt-gui just tells me that it has been submitted here and does not allow me to > report it again. How can I make it forget that report? It isn't important. The thing is, that if you run a deamon in a debug mode, then it prints a lot of information even if the crash is already reported. So, stop the daemon $service abrt stop, and run it in the debug mode from command line $abrt -dvvv. Thanks.
*** Bug 524082 has been marked as a duplicate of this bug. ***
Created attachment 361556 [details] abrtd -dvvv when filing 524082 abrt-0.0.8.5-1.fc12.i686
Created attachment 361557 [details] /var/log/abrt-logger My /var/log/abrt-logger - I don't know if this makes sense to you
*** Bug 523191 has been marked as a duplicate of this bug. ***
*** Bug 522967 has been marked as a duplicate of this bug. ***
*** Bug 522982 has been marked as a duplicate of this bug. ***
*** Bug 523328 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I haven't seen this for a while, so I guess this issue has been fixed?
This has been fixed a while ago.