I see the same behavior: here's a backtrace
[Switching to Thread 0xb672d6b0 (LWP 25300)]
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7c98589 in __lll_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7c93ba6 in _L_lock_95 () from /lib/tls/i686/cmov/libpthread.so.0
#3 0xb7c9358a in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb6f39040 in g_static_rec_mutex_lock () from /usr/lib/libglib-2.0.so.0
#5 0xb5a04d19 in ?? ()
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamelimap.so
#6 0x081056b0 in ?? ()
#7 0x08251618 in ?? ()
#8 0x00000000 in ?? ()
** Changed in: evolution (Ubuntu)
Status: New => Confirmed
--
Hardy - Evolution Hangs on Recovery dialog
https://bugs.launchpad.net/bugs/178452
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
