GNOME Bugzilla – Bug 487049
crash in Panel:
Last modified: 2008-02-23 22:55:42 UTC
Version: 2.20.0.1 What were you doing when the application crashed? Distribution: redhat-4 Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22.1 #1 SMP Sun Jul 22 23:41:14 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: Lush Memory status: size: 408805376 vsize: 408805376 resident: 22122496 share: 7544832 rss: 22122496 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191656001 rtime: 291224 utime: 276401 stime: 14823 cutime:0 cstime: 33 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (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 0x2b7e46632ea0 (LWP 27856)] [New Thread 0x40040950 (LWP 4245)] (no debugging symbols found) 0x00002b7e40535c7f in waitpid () from /lib/libpthread.so.0
+ Trace 170497
Thread 1 (Thread 0x2b7e46632ea0 (LWP 27856))
----------- .xsession-errors (2474823 sec old) --------------------- (evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13 *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed (evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13 (evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13 *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed (evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13 (evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13 ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 508603 has been marked as a duplicate of this bug. ***
*** Bug 508373 has been marked as a duplicate of this bug. ***
*** Bug 504884 has been marked as a duplicate of this bug. ***
*** Bug 487243 has been marked as a duplicate of this bug. ***
*** Bug 493905 has been marked as a duplicate of this bug. ***
*** Bug 498592 has been marked as a duplicate of this bug. ***
*** Bug 503257 has been marked as a duplicate of this bug. ***
*** Bug 503736 has been marked as a duplicate of this bug. ***
*** Bug 505003 has been marked as a duplicate of this bug. ***
*** Bug 518293 has been marked as a duplicate of this bug. ***