abrt 1.0.4 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault comment: When I shut down my box, the OpenOffice Quickstarter was running in the toolbar. I'm guessing the Quickstarter wasn't happy about being shut down this way. component: openoffice.org executable: /usr/lib/openoffice.org3/program/soffice.bin kernel: 2.6.31.12-174.2.3.fc12.i686.PAE package: openoffice.org-brand-1:3.1.1-19.14.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault) release: Fedora release 12 (Constantine) How to reproduce ----- 1. shut down the computer 2. 3.
Created attachment 387819 [details] File: backtrace
I suppose it crashed because LockHelper::getGlobalLock(), which just forwards to osl::Mutex::getGlobalMutex(), had already been destroyed. dtardon->jim: Is the crash reproducible on your machine?
The gtk quick starter still shows some signs of bustage in 3.2 despite the recent efforts to fix it up. I'm not certain that the above crash is due to the qstart bustage, but it definitely doesn't improve the situation and may be a contributor.
Checked in a set of quick starter fixes for the various things wrong with it that I can see. Will be in >= 3.1.1-19.25
(In reply to comment #2) > I suppose it crashed because LockHelper::getGlobalLock(), which just forwards > to osl::Mutex::getGlobalMutex(), had already been destroyed. > > dtardon->jim: Is the crash reproducible on your machine? It has only done t that one time that I have seen. It was, I believe, the 1st time I shut down the computer after activating the Quickstarter. Maybe that had something to do with it. I am still trying to get the hang of this abrt thing as well. It sometime shows me crashes that I didn't/wouldn't know I had if abrt didn't tell me :) It appears that often something crashes and the system restarts whatever-it-was that crashed without telling me and the only way I even know something happened it the blinking abrt bug in the toolbar. Because of this, it is regularly some minutes before I know something went wrong and I don't know exactly what was happening when it crashed. It often ends up being purely a guess on my part as to why whatever-it-was crashed.
openoffice.org-3.1.1-19.25.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/openoffice.org-3.1.1-19.25.fc12
openoffice.org-3.1.1-19.25.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update openoffice.org'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1460
openoffice.org-3.1.1-19.26.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/openoffice.org-3.1.1-19.26.fc12
openoffice.org-3.1.1-19.26.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 577904 has been marked as a duplicate of this bug. ***
seems it's still present in 3.1.1-19.28.fc12 :(
dtardon->evlyons: can you reproduce the crash? Do you have quickstarter enabled?
evlyons->dtardon: cannot reproduce the crash. Verified under options that quickstarter is not enabled.
I can't reproduce this unfortunately. I had hoped it was due to the quick starter bugs I could see, but as it persisted, and in the absence of a means to reproduce it I'm unable to determine the problem.
*** Bug 581413 has been marked as a duplicate of this bug. ***