Bug 127790 - Crash after trying to stop an in-progress operation for a just deleted account
Summary: Crash after trying to stop an in-progress operation for a just deleted account
Status: RESOLVED DUPLICATE of bug 206877
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-21 23:41 UTC by Vincenzo Ciancia
Modified: 2009-12-26 00:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincenzo Ciancia 2006-05-21 23:41:25 UTC
Version:           1.9.1 (using KDE 3.5.1 Level "a" , SUSE 10.1)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.16.13-4-default

I had set-up an imap account, that I was checking, and the checking was going on a bit slowly. I then deleted the account, and after closing the configuation dialog I saw that it was still checking the account (this is a different bug). Then I clicked on the arrow that opens the progress bars (the one in the bottom of the window) and clicked on the red button to stop downloading unuseful messages. Kmail suddenly crashed.
Comment 1 Bram Schoenmakers 2007-02-04 20:28:46 UTC
Can you still reproduce and if yes, could you provide us a backtrace please?
Comment 2 Vincenzo Ciancia 2007-02-04 21:03:30 UTC
Yes I can reproduce the bug on kmail 1.9.5. Unfortunately I can't provide a backtrace. I downloaded the necessary -dbgsym package from ubuntu, and reproduced the bug, but when the "crash dialog" pops up, it deadlocks with only a few lines of backtrace. If I run kmail in gdb, no need to say it, I can't get a bactkrace at all (I suppose it is because the kmail process is wrapped in the crash capturer process). If you can give me hints on how to get out of this, I will be happy to help. However it is really easy to reproduce the bug if you have an imap account (just ... be quick in deleting the account, but since kmail takes ages on disconnected imap, it will be easy).


Comment 3 Ismail Onur Filiz 2007-02-04 21:53:44 UTC
Try running kmail with "--nofork --nocrashhandler" from within gdb. The first allows you to get a backtrace, whereas the second enables getting a core dump. ( You need to have run 'ulimit -c unlimited' before running gdb for the core dump though )
Comment 4 Vincenzo Ciancia 2007-02-04 23:34:37 UTC
Ok, here it is, I hope it is useful, let me know if you need something more.


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1249953344 (LWP 7221)]
0x0842abf1 in ?? ()
(gdb) thread apply all bt

Thread 5 (Thread -1277641840 (LWP 7227)):
#0  0xb7fb77f2 in ?? () from /lib/ld-linux.so.2
#1  0xb63795c6 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb78dec3d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb738b104 in QWaitCondition::wait () from /usr/lib/libqt-mt.so.3
#4  0xb67ced16 in KPIM::ThreadWeaver::Weaver::applyForWork ()
   from /usr/lib/libkdepim.so.1
#5  0xb67cf7c6 in KPIM::ThreadWeaver::Thread::run ()
   from /usr/lib/libkdepim.so.1
#6  0xb703bf21 in QThreadInstance::start () from /usr/lib/libqt-mt.so.3
#7  0xb637531b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb78d23ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 4 (Thread -1269249136 (LWP 7226)):
#0  0xb7fb77f2 in ?? () from /lib/ld-linux.so.2
#1  0xb63795c6 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb78dec3d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb738b104 in QWaitCondition::wait () from /usr/lib/libqt-mt.so.3
#4  0xb67ced16 in KPIM::ThreadWeaver::Weaver::applyForWork ()
   from /usr/lib/libkdepim.so.1
#5  0xb67cf7c6 in KPIM::ThreadWeaver::Thread::run ()
   from /usr/lib/libkdepim.so.1
#6  0xb703bf21 in QThreadInstance::start () from /usr/lib/libqt-mt.so.3
#7  0xb637531b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb78d23ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread -1260856432 (LWP 7225)):
#0  0xb7fb77f2 in ?? () from /lib/ld-linux.so.2
#1  0xb63795c6 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb78dec3d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb738b104 in QWaitCondition::wait () from /usr/lib/libqt-mt.so.3
#4  0xb67ced16 in KPIM::ThreadWeaver::Weaver::applyForWork ()
   from /usr/lib/libkdepim.so.1
#5  0xb67cf7c6 in KPIM::ThreadWeaver::Thread::run ()
   from /usr/lib/libkdepim.so.1
#6  0xb703bf21 in QThreadInstance::start () from /usr/lib/libqt-mt.so.3
#7  0xb637531b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb78d23ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread -1252463728 (LWP 7224)):
#0  0xb7fb77f2 in ?? () from /lib/ld-linux.so.2
#1  0xb63795c6 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb78dec3d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb738b104 in QWaitCondition::wait () from /usr/lib/libqt-mt.so.3
#4  0xb67ced16 in KPIM::ThreadWeaver::Weaver::applyForWork ()
   from /usr/lib/libkdepim.so.1
#5  0xb67cf7c6 in KPIM::ThreadWeaver::Thread::run ()
   from /usr/lib/libkdepim.so.1
#6  0xb703bf21 in QThreadInstance::start () from /usr/lib/libqt-mt.so.3
#7  0xb637531b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb78d23ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1249953344 (LWP 7221)):
#0  0x0842abf1 in ?? ()
Cannot access memory at address 0xffffa218
Comment 5 Björn Ruberg 2009-12-26 00:50:16 UTC

*** This bug has been marked as a duplicate of bug 206877 ***