GNOME Bugzilla – Bug 526242
crash on saving attachment/email
Last modified: 2009-01-20 00:10:56 UTC
What were you doing when the application crashed? I was trying to save an email that I had selected in my inbox. Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-rc8-wl-04519-g6648ff7-dirty #71 PREEMPT Fri Apr 4 22:43:31 CEST 2008 ppc X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: Mist Memory status: size: 317136896 vsize: 317136896 resident: 190341120 share: 28037120 rss: 190341120 rss_rlim: 4294967295 CPU usage: start_time: 1207342074 rtime: 17332 utime: 14894 stime: 2438 cutime:188 cstime: 21 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x48054d60 (LWP 3625)] [New Thread 0x53eff460 (LWP 12831)] [New Thread 0x549ff460 (LWP 12830)] [New Thread 0x4c19f460 (LWP 3682)] [New Thread 0x4a4ff460 (LWP 3681)] [New Thread 0x4bdf6460 (LWP 3668)] [New Thread 0x4b5e5460 (LWP 3640)] [New Thread 0x4acff460 (LWP 3638)] [New Thread 0x49cff460 (LWP 3635)] [New Thread 0x4933c460 (LWP 3634)] [New Thread 0x48b3c460 (LWP 3633)] (no debugging symbols found) 0x0f96b9e8 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
+ Trace 194247
Thread 2 (Thread 0x53eff460 (LWP 12831))
----------- .xsession-errors (14 sec old) --------------------- Couldn't Get password 9 ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) camel-Message: -- GLib-GObject-ERROR **: g_type_plugin_*() invalidly modified type `GLocalFileEnumerator' aborting... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
I have a number of debug packages installed now... maybe this helps Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-wl-06933-g0bacadf-dirty #161 PREEMPT Mon May 5 18:32:47 CEST 2008 ppc X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: Mist Memory status: size: 380010496 vsize: 380010496 resident: 276680704 share: 28155904 rss: 276680704 rss_rlim: 4294967295 CPU usage: start_time: 1210009906 rtime: 79290 utime: 68782 stime: 10508 cutime:760 cstime: 156 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x48056950 (LWP 4181)] [New Thread 0x57fff460 (LWP 7885)] [New Thread 0x4b5ff460 (LWP 7882)] [New Thread 0x4a33a460 (LWP 7865)] [New Thread 0x4bf9f460 (LWP 4270)] [New Thread 0x4bf5f460 (LWP 4269)] [New Thread 0x49b3a460 (LWP 4214)] 0x0f71a9e8 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
+ Trace 196972
Thread 3 (Thread 0x4b5ff460 (LWP 7882))
----------- .xsession-errors (20 sec old) --------------------- (evolution:4181): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: No matching results) (evolution:4181): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: No matching results) (evolution:4181): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: No matching results) (evolution:4181): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: No matching results) (evolution:4181): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: No matching results) Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c0001f (Archive Ma) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. GLib-GObject-ERROR **: g_type_plugin_*() invalidly modified type `GLocalFileEnumerator' aborting... --------------------------------------------------
Oh, mind you, in the second trace I was merely trying to save an attachment, not even a full email. Also, I thought this bug was quite recent, has evolution made a 2.12 -> 2.22 version jump or did something go wrong first?
Much better, thanks. And yes, Evo is tracking GNOME's version numbers now. Thread 3 has the goods. Kinda looks like a GIO crash, but I'd like to take a closer look before reassigning. Possibly related to EAttachmentBar.
There's an assertion failure message right at the end there that may be relevant: GLib-GObject-ERROR **: g_type_plugin_*() invalidly modified type `GLocalFileEnumerator' aborting... Anyway, I don't have a clue. If the kernel had crashed I'd know ;)
*** Bug 531771 has been marked as a duplicate of this bug. ***
And this one looks like a duplicate of bug 519387.
I'm quite sure this is related to GLib bug #537555. When you try with some GLib version which includes the patch from there, then this will probably work as expected. Could you try and report back, please? Thanks in advance.
Closing as dup of bug 519387 due to comment #7. *** This bug has been marked as a duplicate of 519387 ***