GNOME Bugzilla – Bug 318526
Stickynotes crashes when Nautilus "show_desktop" is set to false.
Last modified: 2005-11-20 14:59:50 UTC
Distribution/Version: Slackware 10.2/Gnome GWARE 2.12.0 Steps to reproduce the crash: 1. On any panel, right click, Add to Panel.., Sticky Notes. Sticky Notes applet starts and places itself in selected panel. 2. Restart session. Sticky Notes placed on panel normally. 3. Go to Applications menu, then System Tools, Configuration Editor. Modify key "/apps/nautilus/preferences/show_desktop" to false (default: true). 4. Restart session. Sticky Notes crash. 5. Restore "show_desktop" key to true, restart session, Sticky Notes works again. Expected Results: Desktop hidden and Sticky Notes loaded on panel How often does this happen? Always Additional Information: Debugging Information: 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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 1661)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x4099f8b8 in waitpid () from /lib/libpthread.so.0
+ Trace 63467
Thread 1 (Thread 16384 (LWP 1661))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. *** This bug has been marked as a duplicate of 310370 ***