GNOME Bugzilla – Bug 637396
Hang when moving folders from mbox account to the new default maildir account
Last modified: 2013-09-14 16:53:42 UTC
0x001b8424 in __kernel_vsyscall () Traceback (most recent call last): File "/usr/share/gdb/auto-load/lib/libgobject-2.0.so.0.2704.0-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace Missing separate debuginfos, use: debuginfo-install ibus-gtk2-1.3.99.20101202-1.fc15.i686 ibus-libs-1.3.99.20101202-1.fc15.i686 (gdb) bt
+ Trace 225156
Another hang. This time when opening a folder for the first time after having moved it to maildir: 0x0082c424 in __kernel_vsyscall () Traceback (most recent call last): File "/usr/share/gdb/auto-load/lib/libgobject-2.0.so.0.2704.0-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace Missing separate debuginfos, use: debuginfo-install ibus-gtk2-1.3.99.20101202-1.fc15.i686 ibus-libs-1.3.99.20101202-1.fc15.i686 (gdb) bt
+ Trace 225158
It's hard to debug deadlocks without seeing traces for all the threads. Can you capture a full trace with "thread apply all bt" instead of just "bt" please?
Removing GNOME 3.0 target since there's not enough information here to do anything.
Could this possibly have happened because gnome-terminal ran out of file descriptors? There was a fd leak in g-t at the time I ran these things and I had CAMEL_DEBUG=all running in the terminal...
That's possible. We may also be leaking file descriptors -- it's happened before. If you can still reproduce this, a complete backtrace should all threads would be really helpful.
*showing all threads
I tried moving a folder with 35k messages from mbox to maildir now without having any problems. Had enabled CAMEL_DEBUG=all in the terminal window during the move too.