GNOME Bugzilla – Bug 463230
crash in Evolution: fetching mails
Last modified: 2007-08-17 08:39:03 UTC
What were you doing when the application crashed? fetching mails Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-powerpc #1 Tue Jul 10 19:09:48 CEST 2007 ppc X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 131362816 vsize: 131362816 resident: 60383232 share: 20762624 rss: 60383232 rss_rlim: 4294967295 CPU usage: start_time: 1186168218 rtime: 5610 utime: 5029 stime: 581 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' (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 805592512 (LWP 1255)] [New Thread 852124880 (LWP 1422)] [New Thread 851195088 (LWP 1298)] [New Thread 842802384 (LWP 1297)] [New Thread 823649488 (LWP 1268)] [New Thread 832038096 (LWP 1267)] [New Thread 815260880 (LWP 1264)] (no debugging symbols found) 0x0f1ed5a4 in ?? () from /lib/libpthread.so.0
+ Trace 152618
Thread 4 (Thread 842802384 (LWP 1297))
----------- .xsession-errors (4846876 sec old) --------------------- /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "zhaojin" /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/lager:/tmp/.ICE-unix/3847 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 ** Message: Not starting remote desktop server Window manager warning: Failed to read saved session file /home/zhaojin/.metacity/sessions/1104908500-4468-1284404231.ms: Failed to open file '/home/zhaojin/.metacity/sessions/1104908500-4468-12844042 The application 'x-session-manager' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. --------------------------------------------------
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 339602 ***