GNOME Bugzilla – Bug 354760
crash in Sticky Notes: I was starting gnome. it...
Last modified: 2006-11-10 16:06:14 UTC
What were you doing when the application crashed? I was starting gnome. it crashed before when I added the applet, which seamed to lock the system into an infinite bug-buddy loop (including gnome-panel crashing I think). If this continues, you'll get a second report. Distribution: Unknown Gnome Release: 2.15.92 2006-08-23 (Frugalware) BugBuddy Version: 2.15.92 Memory status: size: 152178688 vsize: 152178688 resident: 9699328 share: 6828032 rss: 9699328 rss_rlim: -1 CPU usage: start_time: 1157634801 rtime: 8 utime: 7 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/stickynotes_applet' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47075237507280 (LWP 2849)] (no debugging symbols found) 0x00002ad08cbcb855 in waitpid () from /lib/libpthread.so.0
+ Trace 71792
Thread 1 (Thread 47075237507280 (LWP 2849))
I was running Xgl with compiz at the time, if that matters. When sticky notes crashed, bug-buddy popped up again and again. When login in afresh, gnome-panel again started Sticky Notes (and failed). I had to disable it via GConf - I believe it might be better if gnome-panel automatically disabled applets that crash at startup.
*** Bug 353031 has been marked as a duplicate of this bug. ***
I was (unknowingly ;) ) half-way through a gnome upgrade at the time. It works fine now (gnome 2.16.0), with and without compiz. Seeing the age of the duplicate bug, this may have been a bug in an early pre-release of gnome as shipped in Frugalware.
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME. I'm marking this bug as obsolete, since it was encountered in a previous version of Gnome, and as you have mentioned, is not seen in the latest version.