GNOME Bugzilla – Bug 489288
crash in backend_died_cb at calendar-sources.c:432
Last modified: 2008-01-10 08:50:41 UTC
Version: 2.20.0.1 What were you doing when the application crashed? evolution --force-shutdown Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Kallisti Icon Theme: Gion Memory status: size: 82292736 vsize: 82292736 resident: 32342016 share: 15187968 rss: 32342016 rss_rlim: 4294967295 CPU usage: start_time: 1193039115 rtime: 9064 utime: 8485 stime: 579 cutime:0 cstime: 11 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ea86b0 (LWP 16223)] [New Thread 0xb622ab90 (LWP 15564)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 172140
Thread 1 (Thread 0xb6ea86b0 (LWP 16223))
----------- .xsession-errors (45997 sec old) --------------------- File "/usr/share/system-config-printer/applet.py", line 648, in refresh self.check_state_reasons (c, my_printers) File "/usr/share/system-config-printer/applet.py", line 530, in check_state_reasons self.notify.attach_to_status_icon (self.statusicon) AttributeError: 'pynotify.Notification' object has no attribute 'attach_to_status_icon' ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File "/var/lib/python-support/python2.4/dbus/connection.py", line 214, in maybe_handle_message self._handler(*args, **kwargs) File "/usr/share/system-config-printer/applet.py", line 791, in handle_dbus_signal self.refresh () File "/usr/share/system-config-printer/applet.py", line 648, in refresh self.check_state_reasons (c, my_printers) File "/usr/share/system-config-printer/applet.py", line 5 ...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!
Hi ! I upgraded my Debian unstable gnome and I do not have this crash anymore. Cheers, Romain.
*** Bug 501867 has been marked as a duplicate of this bug. ***
*** Bug 507792 has been marked as a duplicate of this bug. ***
Okay, here comes a full backtrace. Please reopen the bug. If I can do anything else, just ask. Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 61042688 vsize: 61042688 resident: 20873216 share: 13164544 rss: 20873216 rss_rlim: 4294967295 CPU usage: start_time: 1199950967 rtime: 214 utime: 200 stime: 14 cutime:0 cstime: 0 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 0xb6fbd6b0 (LWP 26500)] [New Thread 0xb6522b90 (LWP 26544)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 184752
Thread 1 (Thread 0xb6fbd6b0 (LWP 26500))
thanks a lot!
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 378854 ***