GNOME Bugzilla – Bug 587874
Crash in emfv_got_folder at em-folder-view.c line 774
Last modified: 2013-08-07 12:40:40 UTC
What were you doing when the application crashed? Started evolution from the panel menu. Waited a couple of minutes and did it again when nothing happened. When they both eventually turned up, I clicked the close button on one of them. Clicked 'wait' when the window manager told me it wasn't responding and asked if I wanted to force it to quit. Then it died anyway. Distribution: Fedora release 11 (Leonidas) Gnome Release: 2.26.2 2009-06-01 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.30-6.fc12.x86_64 #1 SMP Fri Jun 12 11:36:05 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10601901 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 1915060224 vsize: 1915060224 resident: 71184384 share: 25964544 rss: 71184384 rss_rlim: 18446744073709551615 CPU usage: start_time: 1246877758 rtime: 931 utime: 622 stime: 309 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f3425b8b910 (LWP 8201)] [New Thread 0x7f342518a910 (LWP 8198)] [New Thread 0x7f3426bfd910 (LWP 8189)] [New Thread 0x7f34657fb910 (LWP 8171)] [New Thread 0x7f34675fe910 (LWP 8170)] [New Thread 0x7f342cdfa910 (LWP 8168)] [New Thread 0x7f342d7fb910 (LWP 8167)] [New Thread 0x7f342e1fc910 (LWP 8165)] [New Thread 0x7f342ebfd910 (LWP 8164)] [New Thread 0x7f342f5fe910 (LWP 8163)] [New Thread 0x7f342ffff910 (LWP 8162)] [New Thread 0x7f3448dc7910 (LWP 8161)] [New Thread 0x7f34497c8910 (LWP 8160)] [New Thread 0x7f3467fff910 (LWP 8159)] [New Thread 0x7f344a1c9910 (LWP 8158)] [New Thread 0x7f344abca910 (LWP 8157)] [New Thread 0x7f344bfff910 (LWP 8156)] [New Thread 0x7f34661fc910 (LWP 8152)] [New Thread 0x7f346cfa7910 (LWP 8148)] [New Thread 0x7f346d9a8910 (LWP 8147)] 0x0000003ea200e9dd in __libc_waitpid (pid=8228, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); Current language: auto; currently minimal
+ Trace 216336
Thread 1 (Thread 0x7f347a1b57f0 (LWP 7995))
----------- .xsession-errors (15 sec old) --------------------- warning: the debug information found in "/usr/lib/debug/usr/lib64/gio/modules/libgvfsdbus.so.debug" does not match "/usr/lib64/gio/modules/libgvfsdbus.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libgvfscommon.so.0.0.0.debug" does not match "/usr/lib64/libgvfscommon.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64/libgvfscommon.so.0.0.0.debug" does not match "/usr/lib64/libgvfscommon.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/gio/modules/libgioremote-volume-monitor.so.debug" does not match "/usr/lib64/gio/modules/libgioremote-volume-monitor.so" (CRC mismatc warning: the debug information found in "/usr/lib/debug/usr/lib64/gio/modules/libgioremote-volume-monitor.so.debug" does not match "/usr/lib64/gio/modules/libgioremote-volume-monitor.so" (CRC mismatch --------------------------------------------------
*** Bug 587859 has been marked as a duplicate of this bug. ***
*** Bug 590910 has been marked as a duplicate of this bug. ***
*** Bug 593300 has been marked as a duplicate of this bug. ***
Same crash with exchange account on 2.28.2 in downstream bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=551624
The code path that's crashing has not existed in the code base for several years now. I looked at it briefly, and it looks like the problem was that the EMFolderView was freed before the callback tried to use it. Is this something we still want to fix in older versions (pre-3.0)?
You're welcome to take it upon yourself to fix older versions if you want, but nowadays the upstream team only maintains the latest release branch (currently gnome-3-8) and the master development branch. We're too few in number to take on any larger commitment.
Closing as OBSOLETE. Please reopen if the bug resurfaces in newer versions.