GNOME Bugzilla – Bug 487797
crash in Evolution: Εξαναγκασμός σε έξοδο
Last modified: 2007-10-18 23:20:10 UTC
What were you doing when the application crashed? Εξαναγκασμός σε έξοδο Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 456548352 vsize: 456548352 resident: 34717696 share: 20086784 rss: 34717696 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192693327 rtime: 2420 utime: 2404 stime: 16 cutime:1 cstime: 3 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 0x2abbc209ef90 (LWP 7566)] [New Thread 0x42845950 (LWP 7606)] [New Thread 0x42804950 (LWP 7605)] [New Thread 0x42003950 (LWP 7604)] [New Thread 0x41802950 (LWP 7603)] [New Thread 0x41001950 (LWP 7585)] [New Thread 0x40800950 (LWP 7584)] (no debugging symbols found) 0x00002abbb9f8cc7f in waitpid () from /lib/libpthread.so.0
+ Trace 171065
Thread 1 (Thread 0x2abbc209ef90 (LWP 7566))
----------- .xsession-errors (25 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (epiphany:7284): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed evolution-shell-Message: Killing old version of evolution-data-server... The application 'evolution-2.10' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. evolution-shell-Message: Killing old version of evolution-data-server... --------------------------------------------------
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 426496 ***