abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: simdock component: simdock executable: /usr/bin/simdock kernel: 2.6.35.6-48.fc14.i686 package: simdock-1.2-10.fc14 rating: 3 reason: Process /usr/bin/simdock was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1288956460 uid: 500 How to reproduce ----- 1. run simdock 2. can't read firefox.jpg file 3. crash
Created attachment 458050 [details] File: backtrace
Thanks for your report, I am not able to reproduce. When firefox.jpg is missing I get a warning, however no crash. Can you attach ~/.SimDock/launchers.xml ̃ ~/.gconf/apps/simdock/%gconf.xml files to the bug report?
Created attachment 458928 [details] SimDock launcher My Simdock launcher file...
(In reply to comment #2) > Thanks for your report, > > I am not able to reproduce. > > When firefox.jpg is missing I get a warning, however no crash. > > Can you attach > > ~/.SimDock/launchers.xml > ̃ ~/.gconf/apps/simdock/%gconf.xml > > files to the bug report? I have a launcher file which I include but the other file does not exist... $ ls -l ~/.SimDock total 4 -rw-rw-r--. 1 akornak akornak 184 Nov 5 06:27 launchers.xml $ ls -l ~/.gconf/apps/simdock/%gconf.xml ls: cannot access /home/akornak/.gconf/apps/simdock/%gconf.xml: No such file or directory $ ls -la ~/.gconf/apps/ total 16 drwx------. 4 root root 4096 Nov 5 22:30 . drwx------. 3 root root 4096 Nov 6 20:20 .. -rw-------. 1 root root 0 Nov 5 20:55 %gconf.xml drwx------. 3 root root 4096 Nov 5 20:55 nautilus drwx------. 3 root root 4096 Nov 5 23:20 totem $ yum list simdock Installed Packages simdock.i686 1.2-10.fc14 @fedora
*** Bug 607457 has been marked as a duplicate of this bug. ***
*** Bug 620775 has been marked as a duplicate of this bug. ***
*** Bug 636457 has been marked as a duplicate of this bug. ***
*** Bug 668749 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping