GNOME Bugzilla – Bug 416199
Crash when selecting a new message
Last modified: 2013-09-13 00:50:16 UTC
With evolution-2.9.92-1.fc7.1.x86_64, when selecting a new message Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.92 2007-02-27 (Red Hat, Inc) BugBuddy Version: 2.17.4 System: Linux 2.6.21-0.14.rc3.mm1.fc7 #1 SMP Thu Mar 8 19:58:05 CET 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10299901 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 576344064 vsize: 576344064 resident: 46555136 share: 20148224 rss: 46555136 rss_rlim: 18446744073709551615 CPU usage: start_time: 1173381730 rtime: 1209 utime: 1065 stime: 144 cutime:3 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47707164544912 (LWP 3859)] [New Thread 1082132800 (LWP 4385)] [New Thread 1090525504 (LWP 3867)] 0x0000003234e0d83f in __libc_waitpid (pid=4386, stat_loc=0x7ffffb2f740c, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 116990
Thread 1 (Thread 47707164544912 (LWP 3859))
----------- .xsession-errors (324 sec old) --------------------- thread 0xd23930 started for pool 0x9e50d0. thread 0xd23930 in pool 0x9e50d0 waits for up to a 1/2 second for task (1 running, 1 unprocessed). thread 0xd23930 in pool 0x9e50d0 calling func. thread 0xd23930 in pool 0x9e50d0 waits for up to a 1/2 second for task (1 running, 0 unprocessed). thread 0xd23930 leaving pool 0x9e50d0 for global pool. Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x7a00ec7 (Py3k2007Py) Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x7a00ec7 (Py3k2007Py) Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x7a00ec7 (Py3k2007Py) Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x7a00ec7 (Py3k2007Py) Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x7a00ec7 (Py3k2007Py) Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Can you reproduce this while running Evolution under gdb? See http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details how to do this.
this is the same issue as bug 431459 which has an even better trace. therefore marking as duplicate. *** This bug has been marked as a duplicate of 431459 ***