After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 316544 - Sticky Notes crashes after update
Sticky Notes crashes after update
Status: RESOLVED DUPLICATE of bug 310370
Product: gnome-applets
Classification: Other
Component: stickynotes
2.12.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-17 08:03 UTC by Luca Merolla
Modified: 2010-01-24 01:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Luca Merolla 2005-09-17 08:03:33 UTC 
After a successfully update from gnome-2.10 to gnome-2.12 the stickynotes_applet
crashes on startup.
Comment 1 Yanko Kaneti 2005-10-06 22:51:05 UTC 
Thanks for the bug report. Without a stack trace from the crash it's very hard
to determine what caused it.
Can you provide us with one? Please see [WWW]http://live.gnome.org/GettingTraces
for more information on how to do so.
Comment 2 Luca Merolla 2005-10-07 07:00:11 UTC 
Ok, this is the BT. I Hope it helps:

[Thread debugging using libthread_db enabled]
[New Thread -1222138176 (LWP 10840)]

** (stickynotes_applet:10840): WARNING **: not able to get desktop window id

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222138176 (LWP 10840)]
0x08050579 in applet_check_click_on_desktop_cb ()
(gdb) thread apply all bt

+ Trace 63405

Thread 1 (Thread -1222138176 (LWP 10840))

  • #0 applet_check_click_on_desktop_cb
  • #1 ??
  • #2 ??
  • #3 pthread_mutex_lock
    from /lib/tls/libpthread.so.0 






Comment 3


Danielle Madeley





          2006-01-11 04:40:26 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 310370 ***