GNOME Bugzilla – Bug 460204
crash in Evolution Mail: I've alredy open a few a...
Last modified: 2008-10-01 15:49:11 UTC
What were you doing when the application crashed? I've alredy open a few application like iceweasel, nautilus, konsole, KFTPgrabber, amarok, amsn and Kregator. I've try to add a tar.gz file to a new email. The file wasn't so big, only 3,3Kb. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21 #1 SMP PREEMPT Mon Jun 25 11:43:48 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaFancyCandy Icon Theme: Gion Memory status: size: 146403328 vsize: 146403328 resident: 39501824 share: 22781952 rss: 39501824 rss_rlim: 4294967295 CPU usage: start_time: 1185357037 rtime: 1628 utime: 1378 stime: 250 cutime:28 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1210370384 (LWP 4296)] [New Thread -1296155760 (LWP 6559)] [New Thread -1270801520 (LWP 4660)] [New Thread -1250976880 (LWP 4658)] [New Thread -1270535280 (LWP 4648)] [New Thread -1242584176 (LWP 4611)] [New Thread -1234191472 (LWP 4601)] [New Thread -1225798768 (LWP 4600)] [New Thread -1217406064 (LWP 4599)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 150419
Thread 1 (Thread -1210370384 (LWP 4296))
----------- .xsession-errors (5768 sec old) --------------------- ** (nm-applet:4185): WARNING **: <WARNING> nma_dbus_init (): nma_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.14" is not allowed to own the service "or ** (nm-applet:4185): WARNING **: <WARNING> nma_dbus_init (): nma_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.14" is not allowed to own the service "or ** (nm-applet:4185): WARNING **: <WARNING> nma_dbus_init (): nma_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.14" is not allowed to own the service "or ** (nm-applet:4185): WARNING **: <WARNING> nma_dbus_init (): nma_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.14" is not allowed to own the service "or ** (nm-applet:4185): WARNING **: <WARNING> nma_dbus_init (): nma_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.14" is not allowed to own the service "or ...Too much output, ignoring rest... --------------------------------------------------
can you add that man page tar.gz file here, for testing? (only if it does not contain any confidential data) thanks in advance!
Created attachment 92926 [details] The file that i've try to attach
Hmm, I dont seem to reproduce this at all. I traversed through the entire code and I dont see a way this can happen. When a mime_part is created it is set a default mime type and looks like it is null for you? Does the crash happens when you attach any file or just this? Is it reproducible always?
Unable to reproduce on my side also ... Any clues on how to reproduce it.. ?
Mmm... I remember that evolution have crashed when it have tried to attach the file, after I've click ok. I've too many application open and i use Debian Testing, perhaps the bug is in the Debian package...
What kind of a attachment it was ? just attach it here in for the testing purpose if dont have any confidential data..
I've already attach the file... Is a tar.gz with translated man pages.
*** Bug 487368 has been marked as a duplicate of this bug. ***
*** Bug 491533 has been marked as a duplicate of this bug. ***
*** Bug 489809 has been marked as a duplicate of this bug. ***
I suspect there should be some duplicates for this. I have fixed this problem and committed to: Trunk: http://svn.gnome.org/viewvc/evolution-data-server?view=revision&revision=8344 Evo 2.12 branch: http://svn.gnome.org/viewvc/evolution-data-server?view=revision&revision=8345
I reverted this in both trunk (Committed revision 8349) and stable (Committed revision 8350) because it doesn't play well with prefer plain plugin and HTML mails. Hence reopening.
Sankar, I looked at it a bit and you used bad function there, you used camel_data_wrapper_get_mime_type which returns char *, but the function expects CamelContentType *, thus you should use camel_data_wrapper_get_mime_type_field. It was the reason of compiler warning I told you. Compiler was right this time. It was serious warning. :)
Sankar ping. Btw, if you believe it will fix it, then you should fix all accesses to mime_type member in that file, because the direct access to that private property is used there so many times. I believe your fix is correct, but I'm not sure if it will fix this particular bug :)
I guess using that function will not fix the problem. Direct access is fine I guess.
Ubuntu bug on this: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/195788. This is 2.21.92, and reporter states he can always reproduce it.
hggdh, feel free to adjust the version info of the report, then :)
Created attachment 106571 [details] [review] proposed evo patch for evolution; We debugged it with hggdh and Effenberg remotely (my apologize I disappeared so quickly, my connection got lost suddenly and I didn't know the reason until now) and we found the gnome_vfs can return invalid mime_types, like empty strings, and in that case the mime_type member is finally set to NULL in camel-mime-part.c:process_header with HEADER_CONTENT_TYPE as the part of call to camel_medium_set_content_object from e-attachment.c. The attached patch tries to parse returned mime type and if that fails it returns NULL.
i wonder if gvfs/gio suffer under the same issue like gnome-vfs.
Milan, go for it in trunk after freeze. Great work guys.
Bumping version to a stable release.
for 2.22.x and 2.23.1
Committed to trunk. Committed revision 35184. Committed to gnome-2-22. Committed revision 35185.
*** Bug 523046 has been marked as a duplicate of this bug. ***
*** Bug 525855 has been marked as a duplicate of this bug. ***
*** Bug 526693 has been marked as a duplicate of this bug. ***
*** Bug 533298 has been marked as a duplicate of this bug. ***
*** Bug 543336 has been marked as a duplicate of this bug. ***
*** Bug 534082 has been marked as a duplicate of this bug. ***