After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 472469 - crash in Evolution: deleting a imap folder w...
crash in Evolution: deleting a imap folder w...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-01 08:23 UTC by bugreports
Modified: 2009-06-22 06:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description bugreports 2007-09-01 08:23:39 UTC
What were you doing when the application crashed?
deleting a imap folder with just deleted mails in it (not yet expunged)


Distribution: Debian 3.1 (sarge)
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.23-rc4-sonne #46 SMP PREEMPT Tue Aug 28 09:32:59 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 182648832 vsize: 182648832 resident: 70422528 share: 24068096 rss: 70422528 rss_rlim: 4294967295
CPU usage: start_time: 1188633252 rtime: 3968 utime: 3059 stime: 909 cutime:1006 cstime: 166 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.10'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233512784 (LWP 4575)]
[New Thread -1321206896 (LWP 9217)]
[New Thread -1319539824 (LWP 5061)]
[New Thread -1289753712 (LWP 4827)]
[New Thread -1310721136 (LWP 4815)]
[New Thread -1298146416 (LWP 4787)]
[New Thread -1281361008 (LWP 4784)]
[New Thread -1271698544 (LWP 4733)]
[New Thread -1259848816 (LWP 4720)]
[New Thread -1251456112 (LWP 4716)]
[New Thread -1242936432 (LWP 4711)]
0xb7f87410 in __kernel_vsyscall ()

Thread 1 (Thread -1233512784 (LWP 4575))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 segv_redirect
    at main.c line 427
  • #4 <signal handler called>
  • #5 camel_message_info_uint32
    at camel-folder-summary.c line 2985
  • #6 vee_info_uint32
    at camel-vee-summary.c line 71
  • #7 camel_message_info_uint32
    at camel-folder-summary.c line 2985
  • #8 vtrash_getv
    at camel-vtrash-folder.c line 141
  • #9 camel_object_get
    at camel-object.c line 1605
  • #10 camel_folder_get_unread_message_count
    at camel-folder.c line 584
  • #11 update_1folder
    at mail-folder-cache.c line 367
  • #12 folder_changed
    at mail-folder-cache.c line 462
  • #13 camel_object_trigger_event
    at camel-object.c line 1511
  • #14 vtrash_folder_changed
    at camel-vtrash-folder.c line 486
  • #15 folder_changed
    at camel-vee-folder.c line 1461
  • #16 camel_object_trigger_event
    at camel-object.c line 1511
  • #17 thaw
    at camel-folder.c line 1583
  • #18 imap_thaw
    at camel-imap-folder.c line 2679
  • #19 camel_folder_thaw
    at camel-folder.c line 1601
  • #20 emfu_delete_rec
    at em-folder-utils.c line 405
  • #21 emfu_delete_response
    at em-folder-utils.c line 426
  • #22 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
  • #26 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (15 sec old) ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
BBDB spinning up...
(gnome-terminal:3668): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
restoring draft flag 'text/plain'
DEBUG: INBOX/debian-legal/debian-legal (imap://newsgate@mail.nn7.de/INBOX/debian-legal/debian-legal)
(evolution-2.10:4575): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4575): camel-WARNING **: Cannot load summary file: `/home/sonne/.evolution/mail/imap/newsgate@mail.nn7.de/folders/INBOX/subfolders/debian-legal/subfolders/debian-legal2/summary-meta': 
(evolution-2.10:4575): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.10:4575): camel-WARNING **: camel_exception_get_id called with NULL parameter.
--------------------------------------------------
Comment 1 Milan Crha 2008-02-26 19:30:56 UTC
The patch for bug #324168 will help with this probably, but not enough. I guess the messages from the deleted folder still kept in the search folder, even they should be removed immediately from there, that's the reason. I will check if I can reproduce myself.
Comment 2 Milan Crha 2008-02-27 17:50:15 UTC
I tried, and I can see similar warning messages on my console, namely:
camel-WARNING **: camel_exception_get_id called with NULL parameter.
twice in a row and then just
camel-WARNING **: Cannot load summary file: `/home/..../summary-meta': Resource temporarily unavailable

Those messages appear in this order, so a bit different from that yours, but pretty same. I also see the last message is more verbose now, which probably indicates some work here, except of the bug I mentioned above.

I can try to find place where the messages come from, but I'm not sure if it worth it (aka I just need an approval from some developer - say Matt?)
Comment 3 Matthew Barnes 2008-02-27 20:22:19 UTC
Milan, try setting a breakpoint on g_logv.  That will stop the process whenever it's about to print a WARNING or other message, then you can get a backtrace.

"Resource temporarily unavailable" usually means an I/O operation has returned error code EAGAIN and the logic needs to try the operation again later.

I haven't really read the rest of the thread closely.  Hope this helps.
Comment 4 Milan Crha 2008-02-28 09:57:44 UTC
To be honest, I intend the question rather as "whether to do that" than "how to do that" :)

There can be some bug in a logic in case the folder is deleted, which can by indicated by "Resource temporarily unavailable" message, but that's just a guess and because it doesn't crash now, then the time spend on this can be for "nothing", so I decided to rather ask if it worth it. (for 2.23.x of course)
Comment 5 Milan Crha 2008-04-07 14:18:25 UTC
The first message comes from here:
Breakpoint 1, IA__g_logv (log_domain=0x4424b7 "camel", log_level=G_LOG_LEVEL_WARNING, 
    format=0x4424c0 "camel_exception_get_id called with NULL parameter.", args1=0xbfa0a1cc "") at gmessages.c:400
400       log_level &= G_LOG_LEVEL_MASK;
(gdb) bt
  • #0 IA__g_logv
    at gmessages.c line 400
  • #1 IA__g_log
    at gmessages.c line 517
  • #2 camel_exception_get_id
    at camel-exception.c line 240
  • #3 imap_expunge_uids_online
    at camel-imap-folder.c line 1294
  • #4 disco_expunge_uids
    at camel-disco-folder.c line 331
  • #5 disco_expunge
    at camel-disco-folder.c line 354
  • #6 disco_sync
    at camel-disco-folder.c line 278
  • #7 camel_folder_sync
    at camel-folder.c line 276
  • #8 emfu_delete_rec
    at em-folder-utils.c line 402
  • #9 emfu_delete_folders
    at em-folder-utils.c line 424
  • #10 emfu_delete_response
    at em-folder-utils.c line 440
  • #0 IA__g_logv
    at gmessages.c line 400
  • #1 IA__g_log
    at gmessages.c line 517
  • #2 camel_exception_get_id
    at camel-exception.c line 240
  • #3 disco_sync
    at camel-disco-folder.c line 279
  • #4 camel_folder_sync
    at camel-folder.c line 276
  • #5 emfu_delete_rec
    at em-folder-utils.c line 402
  • #6 emfu_delete_folders
    at em-folder-utils.c line 424
  • #7 emfu_delete_response
    at em-folder-utils.c line 440
  • #0 IA__g_logv
    at gmessages.c line 400
  • #1 IA__g_log
    at gmessages.c line 517
  • #2 camel_folder_summary_load
    at camel-folder-summary.c line 607
  • #3 camel_imap_summary_new
    at camel-imap-summary.c line 140
  • #4 imap_forget_folder
    at camel-imap-store.c line 1152
  • #5 delete_folder
    at camel-imap-store.c line 2134
  • #6 camel_store_delete_folder
    at camel-store.c line 416
  • #7 emfu_delete_rec
    at em-folder-utils.c line 406
  • #8 emfu_delete_folders
    at em-folder-utils.c line 424
  • #9 emfu_delete_response
    at em-folder-utils.c line 440

Comment 6 Milan Crha 2008-04-07 14:56:58 UTC
First two are easy to fix, but the third, it doesn't make much sense to me. It says: Cannot load summary file: `....': Resource temporarily unavailable
The documentation says "try again later", but I do not think it will help much.
Comment 7 Akhil Laddha 2008-08-07 05:21:21 UTC
see bug 377715, mostly dup
Comment 8 Akhil Laddha 2009-05-20 07:12:36 UTC
vfolder code had been written in 2.24.x due to camel db summary. It will be really useful if you can try in 2.24.x / 2.26.x and report back, thanks.
Comment 9 Akhil Laddha 2009-06-22 06:10:58 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.26.2 or later), please reopen. thanks in advance.