Description of problem: F-11 is pretty confused about search folders, I have nested search folders (Ie. one search folder just looks inside other search folders) these wedre completely broken in F-10 but appear to work a little bit in F-11, alas. the way they are broken seems to stop evolution getting any new mail. What happens is that I start evolution and it starts doing "Updating Search Folders for 'Zimbra:blah:/INBOX/foo/bar'" through all of my folders, and all my search folders steadily get data in them ... but then at some point it just stops on one of the Updaing lines (never goes away, AFAICS) and from what I can see evolution never gets any more email from that point onwards. Trying to quit hangs, --force-shutdown is the only thing that works. Version-Release number of selected component (if applicable): evolution-0:2.26.3-1.fc11.x86_64 ...although I was using at least 2.26.2-1.fc11 for a while.
Note that I can read email, during this hang ... it just doesn't get new email, AFAICS.
Could you install also debug info packages for evolution, evolution-data-server and gtkhtml3, then attach gdb to a running processes of evolution and evolution-data-server of an almost hanged evolution, and attach here traces of evolution and evolution-data-server, please?. You can do that by: a) invoking a command: $ ps -A | grep evo will show all evolution related processes running, showing their PID. b) get the trace of runnig process with process ID PID: $ gdb --batch --ex "t a a bt" -pid=PID &>bt.log attach that bt.log text file, one for evo and one for eds. Thanks in advance.
Created attachment 351501 [details] evolution gdb --batch --ex "t a a bt" -pid=22492 output
Created attachment 351502 [details] output from: gdb --batch --ex "t a a bt" -pid=22497
Created attachment 351503 [details] output from: gdb --batch --ex "t a a bt" -pid=22518 this is evolution-alarm-notify, middle one was the data server ... first was evo itself.
Thanks for the update. evolution-alarm-notify and evolution-data-server are in idle. Evolution is fighting for a lock over the folder: Thread 5 (Thread 0x7ff1d73f8910 (LWP 22577)): #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136 #1 0x0000003aeba08fe5 in _L_lock_949 () from /lib64/libpthread.so.0 #2 0x0000003aeba08e08 in __pthread_mutex_lock (mutex=0x912360) at pthread_mutex_lock.c:61 #3 0x00007ff1fa901a5e in camel_db_begin_transaction (cdb=0x912340, ex=0x0) at camel-db.c:514 #4 0x00007ff1fb02263a in vee_rebuild_folder (vf=0x9331a0, source=<value optimized out>, ex=<value optimized out>) at camel-vee-folder.c:1228 #5 0x00007ff1f6390f89 in vfolder_adduri_exec (m=0xc738f0) at mail-vfolder.c:273 #6 0x00007ff1f63850ef in mail_msg_proxy (msg=0xc738f0) at mail-mt.c:520 #7 0x0000003aed661eb2 in g_thread_pool_thread_proxy ( data=<value optimized out>) at gthreadpool.c:265 #8 0x0000003aed6608b4 in g_thread_create_proxy (data=0xb42f40) at gthread.c:635 #9 0x0000003aeba0686a in start_thread (arg=<value optimized out>) at pthread_create.c:297 #10 0x0000003aeaede25d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 4 (Thread 0x7ff1ebfff910 (LWP 22651)): #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136 #1 0x0000003aeba08fe5 in _L_lock_949 () from /lib64/libpthread.so.0 #2 0x0000003aeba08e08 in __pthread_mutex_lock (mutex=0x91efd0) at pthread_mutex_lock.c:61 #3 0x00007ff1fb021432 in folder_changed_change ( session=<value optimized out>, msg=<value optimized out>) at camel-vee-folder.c:1540 #4 0x00007ff1fb013e6b in session_thread_proxy (msg=0x7ff1b8215110, session=0x791330) at camel-session.c:597 #5 0x0000003aed661eb2 in g_thread_pool_thread_proxy ( data=<value optimized out>) at gthreadpool.c:265 #6 0x0000003aed6608b4 in g_thread_create_proxy (data=0x7ff1b15f81b0) at gthread.c:635 #7 0x0000003aeba0686a in start_thread (arg=<value optimized out>) at pthread_create.c:297 #8 0x0000003aeaede25d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x0000000000000000 in ?? ()
I was pointed to the upstream bug [1], where is exactly this issue discussed, thus moving it there. [1] http://bugzilla.gnome.org/show_bug.cgi?id=583507
Is it possible for someone to do a build with the patch: http://git.gnome.org/cgit/evolution-data-server/commit/?id=69f12a11f08a79030e0ccd179078b84851d5691f ...even if it's just a kojipkg. As atm. I have to --force-shutdown evolution every time I want to get new email (and half my folders don't work).
Also, it's worth pointing out that if I kill evolution-data-server nothing gets better (and the above commit is to evolution-data-server...).
E-D-S provides the mail library, but it's only used in the Evolution process, not the E-D-S process. I'll roll a new F-11 package with this patch.
evolution-data-server-2.26.3-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/evolution-data-server-2.26.3-2.fc11
evolution-data-server-2.26.3-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update evolution-data-server'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7727
evolution-data-server-2.26.3-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.