GNOME Bugzilla – Bug 532293
crash in Panel: Checking my mails
Last modified: 2008-05-09 06:16:44 UTC
Version: 2.20.3 What were you doing when the application crashed? Checking my mails Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 45637632 vsize: 45637632 resident: 22102016 share: 13910016 rss: 22102016 rss_rlim: 4294967295 CPU usage: start_time: 1210143265 rtime: 11344 utime: 10558 stime: 786 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6e76940 (LWP 6913)] [New Thread 0xb637cb90 (LWP 13016)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 197289
Thread 1 (Thread 0xb6e76940 (LWP 6913))
----------- .xsession-errors --------------------- (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) /usr/lib/bug-buddy/gecko: No such file or directory. ** Message: <info> Vous êtes connecté au réseau câblé. ** Message: Google Group Not found CalDAV Eplugin starting up ... ** (gnome-panel:6913): WARNING **: The calendar backend for file:///home/geoffroy/.evolution/tasks/local/system has crashed. warning: .dynamic section for "/usr/lib/libpng12.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 378854 ***