GNOME Bugzilla – Bug 518205
crash in Evolution Mail:
Last modified: 2008-02-24 13:05:35 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.24 #1 PREEMPT Wed Feb 20 16:31:30 CET 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaScaled Icon Theme: glass-icons Memory status: size: 129003520 vsize: 129003520 resident: 36810752 share: 20631552 rss: 36810752 rss_rlim: 4294967295 CPU usage: start_time: 1203759874 rtime: 331 utime: 307 stime: 24 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 0xb68536d0 (LWP 4998)] [New Thread 0xb19ffb90 (LWP 5063)] [New Thread 0xb2be2b90 (LWP 5057)] [New Thread 0xb362bb90 (LWP 5050)] [New Thread 0xb4630b90 (LWP 5040)] [New Thread 0xb4e39b90 (LWP 5038)] [New Thread 0xb5639b90 (LWP 5037)] [New Thread 0xb5e39b90 (LWP 5036)] (no debugging symbols found) 0xb7c78f91 in waitpid () from /lib/libpthread.so.0
+ Trace 190174
Thread 1 (Thread 0xb68536d0 (LWP 4998))
----------- .xsession-errors (3434343 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... /etc/gdm/Xsession: Executing /usr/bin/gnome-session failed, will try to run x-terminal-emulator (gnome-terminal:29541): Vte-WARNING **: Nessun gestore definito per la sequenza di controllo "device-control-string". (gnome-terminal:29541): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
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 324168 ***