Bug 304391

Summary: kmail-4.8.3-r1 crashed after moving many messages from one IMAP folder to another
Product: [Applications] kontact Reporter: Christian <k>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.8.3   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christian 2012-08-01 18:43:32 UTC
Application: kontact (4.8.3)
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.2
Operating System: Linux 3.3.8-gentoo x86_64
Distribution: "Gentoo Base System release 2.1"

-- Information about the crash:
- What I was doing when the application crashed:
Before the application crashed, I had moved all (about 1000) messages from one IMAP folder to another IMAP folder on the same server. (Online, but it took a while.) When the source folder was shown in KMail as empty, I tried to unsubscribe from that IMAP folder, so I opened the "Manage folder subscriptions" window. But there, nothing at all was marked as subscribed, even for other IMAP accounts and local accounts. So I closed that window and then I closed KMail. That's when I got the crash report. (Or maybe I got the crash report when I tried to restart KMail; I am not sure what happened first.)

- Unusual behavior I noticed:

The icons for the IMAP accounts in the Manage folder subscriptions were wrong. They looked like the icon for local Maildir accounts.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7feb61974780 (LWP 24019))]

Thread 3 (Thread 0x7feb470a2700 (LWP 24020)):
#0  pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007feb5e0816ac in scavengerThread (this=0x7feb5ead00a0) at wtf/FastMalloc.cpp:2495
#2  WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7feb5ead00a0) at wtf/FastMalloc.cpp:1618
#3  0x00007feb59642e9c in start_thread (arg=0x7feb470a2700) at pthread_create.c:301
#4  0x00007feb5ee295cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7feb467a1700 (LWP 24021)):
#0  0x00007feb5ee20653 in *__GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007feb5869bb34 in g_main_context_poll (n_fds=1, fds=0xdcead0, timeout=-1, context=0xdb9e50, priority=<optimized out>) at gmain.c:3402
#2  g_main_context_iterate (context=0xdb9e50, block=1, dispatch=1, self=<optimized out>) at gmain.c:3084
#3  0x00007feb5869bf9f in g_main_context_iteration (context=0xdb9e50, may_block=1) at gmain.c:3152
#4  0x00007feb60289556 in QEventDispatcherGlib::processEvents (this=0xdba190, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#5  0x00007feb60258f92 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007feb60259285 in QEventLoop::exec (this=0x7feb467a0e00, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007feb60155948 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#8  0x00007feb60158027 in QThreadPrivate::start (arg=0xdb98c0) at thread/qthread_unix.cpp:307
#9  0x00007feb59642e9c in start_thread (arg=0x7feb467a1700) at pthread_create.c:301
#10 0x00007feb5ee295cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7feb61974780 (LWP 24019)):
[KCrash Handler]
#6  ref (this=0x48d4890146348d2) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#7  QString (other=..., this=0x7fff55a52ba0) at /usr/include/qt4/QtCore/qstring.h:726
#8  KontactInterface::Plugin::identifier (this=0xeb6970) at /tmp/portage/kde-base/kdepimlibs-4.8.3/work/kdepimlibs-4.8.3/kontactinterface/plugin.cpp:101
#9  0x00007feb615a333d in Kontact::MainWindow::activateInitialPluginModule() () from /usr/lib64/libkontactprivate.so.4
#10 0x00000000004036ba in _start ()

Possible duplicates by query: bug 302939, bug 298328, bug 297233, bug 296199, bug 287446.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-08-01 19:10:58 UTC

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