GNOME Bugzilla – Bug 315173
Crash when dragging embedded message/rfc822 into a folder
Last modified: 2005-10-07 10:03:31 UTC
Distribution/Version: Fedora Core 4 Evolution crashes when I drag and drop an embedded message/rfc822 attachment into a folder: 1. Receive an email message with an attached message/rfc822. 2. Drag its' icon into a mail folder (e.g. into the INBOX). In my case, the mail folder is on my IMAP server. Reproducable every time. Console information emitted by Evolution: (evolution:24346): camel-WARNING **: Invalid root: '/home/future/.evolution/mail/local/Drafts.ibex.index' (evolution:24346): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:24346): camel-WARNING **: block size: 1024 (1024) OK (evolution:24346): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:24346): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:24346): camel-WARNING **: flags: unSYNC (evolution:24346): camel-WARNING **: Invalid root: '/home/future/.evolution/mail/local/Outbox.ibex.index' (evolution:24346): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:24346): camel-WARNING **: block size: 1024 (1024) OK (evolution:24346): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:24346): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:24346): camel-WARNING **: flags: unSYNC (evolution:24346): evolution-mail-WARNING **: couldn't get service : No provider available for protocol `' (evolution:24346): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed (evolution:24346): camel-CRITICAL **: camel_stream_printf: assertion `CAMEL_IS_STREAM (stream)' failed update flow align requesting object classid: attachment.0xa67190.8020.mixed.1 object_found: 1 requesting object classid: attachment.0xa67190.8020.mixed.2 object_found: 1 update flow align
Hmm...the messageInfo is NULL, and it crashes because of that.
Yeah helpful comment. This is where it crashes:
+ Trace 62725
Thread 10 (Thread 131080 (LWP 3202))
do_append just needs to null check info
Michael, should we be able to append message like these? Or should they be rejected?
Created attachment 52717 [details] [review] patch to fix it. Partha, I think that should be allowed, we used 'info' to collect the previous flags, which in this case isn't present, thats where it failed.
Commit to both head and 2.4 branch
committed the fix to both the branches, thanks!
verified using evolution-2.4.1.0.200510061830-0.snap.novell.0.1.