abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: python /usr/lib64/gdesklets/gdesklets-daemon component: gdesklets executable: /usr/bin/python kernel: 2.6.35.6-48.fc14.x86_64 package: gdesklets-0.36.2-3.fc14 reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1290757381 uid: 500 How to reproduce ----- 1. /usr/bin/gdesklets is placed in gnome start programs 2. When doing a normal boot or a reboot then the crash happens at startup of gdesklets I think 3. When starting gdesklets from a shell with gdesklets start all is going ok
Created attachment 463004 [details] File: backtrace
To clarify Point 3 from before: After the crash happend I have to issue a gdesklets restart to bring up the deamon again.
Which desklet did you use prior to be crash?
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.start the app 2.clikkin on the ithem 3.no respons Comment ----- I only start the gdesklets app. ant clikking on a widiit. the widgit dont start and then i got this bug
(In reply to comment #3) > Which desklet did you use prior to be crash? I use six different Desklets one with three instances. 1. GoodWeather display 0.3 2. SlideShow 0.9 3. FTB-info 0.3.2 4. FTB-mem-gauge 0.3.2 5. FTB-cpu-plot 0.3.2 6. 3 Instances of FTB-net-plot 0.3.2 (eth0, eth1, wlan0)
Clock and The calender.
Running above desklets: 1. GoodWeather display 0.3 2. SlideShow 0.9 3. FTB-info 0.3.2 4. FTB-mem-gauge 0.3.2 5. FTB-cpu-plot 0.3.2 6. 3 Instances of FTB-net-plot 0.3.2 (eth0, eth1, wlan0) 7. Clock 8. Calender Unfortunately, I am unable to reproduce the crash related to gdesklets from my hardware (. Apparently the bug is related to python because I noticed the segment fault on those line: Program terminated with signal 11, Segmentation fault. #0 0x00000031e04e532a in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #0 0x00000031e04e532a in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #1 0x00000031e04ea71d in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #2 0x00000031e04eb04d in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 I will assign this report to python maintainer for investigation.
Thank you for taking the time to report this crash. Unfortunately, the stack trace is not very useful in determining the cause of the crash, because it lacks debugging symbols. In order to get a symbolic stack trace, the appropriate debuginfo packages need to be installed. In order to accomplish this, you can run the command: debuginfo-install python Please see http://fedoraproject.org/wiki/StackTraces for more information about stack traces.
(In reply to comment #8) Hi again, I installed the requested debuginfos via > > debuginfo-install python > Also I did : debuginfo-install gdesklets yum install pango-debuginfo yum install glib2-debuginfo yum install gtk2-debuginfo After that I had still 62 missing debug infos reported by abrt so finally I installed yum install kernel-debuginfo-common yum install kernel-debuginfo which was proposed by abrt but still 62 missing debug infos remain. I attached you the renewed backtrace above. If I should install any other debug packages please don't hesitate to request them.
Created attachment 463603 [details] renewed backtrace Renewed backtrace with debuginfos for python and gdesklets installed
*** Bug 652401 has been marked as a duplicate of this bug. ***
*** Bug 658585 has been marked as a duplicate of this bug. ***
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just stoped working 2. 3.
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.During screensaver 2. 3.
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Je venais de me loguer dans FC14 2. 3.
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. During screensaver 2. 3.
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Only tried to run on gnome-shell session 2. 3.
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. clicked on calendar desklet
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Je viens juste de me log et d'arriver sur mon bureau . 2. 3.
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I Believe I quit out of gdesklets? 2. Not sure what happened, Sorry. 3.
gdesklets-0.36.3-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/gdesklets-0.36.3-1.fc13
gdesklets-0.36.3-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gdesklets-0.36.3-1.fc14
gdesklets-0.36.3-1.fc14 has been pushed to the Fedora 14 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 gdesklets'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gdesklets-0.36.3-1.fc14
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. gDesklets started at system startup 2. The crash happened 3.
(In reply to comment #27) > Package: gdesklets-0.36.2-3.fc14 > Architecture: x86_64 > OS Release: Fedora release 14 (Laughlin) > > > How to reproduce > ----- > 1. gDesklets started at system startup > 2. The crash happened > 3. Can you test update posted on Comment #26 to see if the issue is fixed?
Package: gdesklets-0.36.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. start gdesklets 2. gdesklets will crash 3. I used clock in my gdesklets' configuration.
gdesklets-0.36.3-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
gdesklets-0.36.3-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 677528 has been marked as a duplicate of this bug. ***
Also assigned to upstream.
Package: gdesklets-0.36.3-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Opened the "manage gdesklets" window 2. Double-clicked on the clock gdesklet 3.
Package: gdesklets-0.36.3-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Je me suis loggué et s'est arrivé quand le bureau est apparu. 2. 3.
Package: gdesklets-0.36.3-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3..
Dave, I contacted upstream about this bug. They need more details about backtrace and suspected python or pygtk2 being the culprit.
Package: gdesklets-0.36.3-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. turn on computer 2. 3.
Package: gdesklets-0.36.3-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Just login and use firefox, smplayer et. Gdesklet is generally unstable
*** Bug 705195 has been marked as a duplicate of this bug. ***
*** Bug 695133 has been marked as a duplicate of this bug. ***
*** Bug 717418 has been marked as a duplicate of this bug. ***
Would anyone enable debuginfo to generate better backtrace? Upstream is unable to fully reproduce the bug. Thank you.
*** Bug 718429 has been marked as a duplicate of this bug. ***
*** Bug 711912 has been marked as a duplicate of this bug. ***
Package: gdesklets-0.36.3-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Screen was locked when crash occured.
Package: gdesklets-0.36.3-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Was browsing a web page I think, when gdesklets crashed.
Package: gdesklets-0.36.3-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Well, I had removed the "nVidia Thermal and Freqs ver0.3" desklet, leaving only "World Time Banner 0.9" enabled, as I suspected that if any particular desklet were at fault it was likely one that monitored sensors etc. This is not the case, as the crash proves.
Package: gdesklets-0.36.3-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- OK, so it isn't related to a specific deklet since this time I disabled "World Time Banner 0.9" and left only "nVidia Thermal and Freqs ver0.3" enabled and I got the crash - infact 2 crashes in one evening is unusual. So it's not the desklets, just something inherent in python possibly - or that exists in both desklets - either way, a desklet should not cause a python crash.
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