Bug 266646 - kmail error "unknown error" dialog
Summary: kmail error "unknown error" dialog
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 2.0.89
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-19 08:16 UTC by Shawn Starr
Modified: 2013-04-09 08:05 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 Shawn Starr 2011-02-19 08:16:07 UTC
Application: kmail (2.0.89)
KDE Platform Version: 4.6.00 (4.6.0)
Qt Version: 4.7.1
Operating System: Linux 2.6.38-0.rc5.git1.1.fc15.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:

I had noticed Kmail was showing email that was unread/in my trash (spam email). Tried to erase by emptying trash. Minimized window, I suppose it was also trying to connect to POP3 mail server and then crashed.

The stack trace seems to indicate it was connection related.

- Unusual behavior I noticed:

Mail box count in trash was 'stuck' at X items.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f4e8b79b860 (LWP 2077))]

Thread 2 (Thread 0x7f4e7eca6700 (LWP 2122)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x0000003b8ccd60fa in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4
#2  0x0000003b8ccd61e9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#3  0x0000003525607d0b in start_thread (arg=0x7f4e7eca6700) at pthread_create.c:301
#4  0x0000003524adfd3d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f4e8b79b860 (LWP 2077)):
[KCrash Handler]
#6  QHostAddressPrivate::clear (this=0x434f4c2065757274) at kernel/qhostaddress.cpp:292
#7  0x0000003b7f8bd5d7 in QAbstractSocket::disconnectFromHostImplementation (this=0x106bbc0) at socket/qabstractsocket.cpp:2448
#8  0x0000003b7f8bdc9c in QAbstractSocket::qt_metacall (this=0x106bbc0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff0dfe3d20) at .moc/release-shared/moc_qabstractsocket.cpp:114
#9  0x0000003b7e760a24 in QMetaMethod::invoke (this=0x7fff0dfe3f10, object=0x106bbc0, connectionType=Qt::DirectConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1578
#10 0x0000003b7e762bc0 in QMetaObject::invokeMethod (obj=0x106bbc0, member=<optimized out>, type=Qt::DirectConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1151
#11 0x0000003b7f8b7584 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., type=Qt::DirectConnection, member=0x3b7f8e6a70 "disconnectFromHostImplementation", obj=<optimized out>) at ../../src/corelib/kernel/qobjectdefs.h:408
#12 QAbstractSocket::disconnectFromHost (this=<optimized out>) at socket/qabstractsocket.cpp:2343
#13 0x0000003b7f8badb8 in QAbstractSocketPrivate::canReadNotification (this=0x106c030) at socket/qabstractsocket.cpp:640
#14 0x0000003b7f8a9cd1 in event (this=<optimized out>, e=<optimized out>) at socket/qnativesocketengine.cpp:1103
#15 QReadNotifier::event (this=<optimized out>, e=<optimized out>) at socket/qnativesocketengine.cpp:1100
#16 0x0000003b803b72a4 in notify_helper (e=0x7fff0dfe47f0, receiver=0xfa5540, this=0xd561e0) at kernel/qapplication.cpp:4445
#17 QApplicationPrivate::notify_helper (this=0xd561e0, receiver=0xfa5540, e=0x7fff0dfe47f0) at kernel/qapplication.cpp:4417
#18 0x0000003b803bc0a1 in QApplication::notify (this=0x7fff0dfe4b60, receiver=0xfa5540, e=0x7fff0dfe47f0) at kernel/qapplication.cpp:4324
#19 0x0000003b81a42de6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#20 0x0000003b7e7596dc in QCoreApplication::notifyInternal (this=0x7fff0dfe4b60, receiver=0xfa5540, event=0x7fff0dfe47f0) at kernel/qcoreapplication.cpp:732
#21 0x0000003b7e783b57 in sendEvent (event=0x7fff0dfe47f0, receiver=<optimized out>) at kernel/qcoreapplication.h:215
#22 socketNotifierSourceDispatch (source=0xd59a20) at kernel/qeventdispatcher_glib.cpp:110
#23 0x0000003528242a9d in g_main_dispatch (context=0xd588e0) at gmain.c:2440
#24 g_main_context_dispatch (context=0xd588e0) at gmain.c:3013
#25 0x0000003528243278 in g_main_context_iterate (context=0xd588e0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3091
#26 0x0000003528243509 in g_main_context_iteration (context=0xd588e0, may_block=1) at gmain.c:3154
#27 0x0000003b7e78441f in QEventDispatcherGlib::processEvents (this=0xd08ef0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#28 0x0000003b804596ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207
#29 0x0000003b7e7588e2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#30 0x0000003b7e758adf in QEventLoop::exec (this=0x7fff0dfe4a30, flags=...) at kernel/qeventloop.cpp:201
#31 0x0000003b7e75ccd7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#32 0x0000000000402ca0 in ?? ()
#33 0x0000003524a212fd in __libc_start_main (main=0x4022e0, argc=3, ubp_av=0x7fff0dfe4fb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff0dfe4fa8) at libc-start.c:226
#34 0x0000000000403195 in _start ()

Reported using DrKonqi
Comment 1 Tobias Koenig 2011-06-04 12:44:25 UTC
Hej Shawn,

can you still reproduce it with a more current version?

Ciao,
Tobias
Comment 2 Shawn Starr 2011-06-05 05:52:47 UTC
Well, don't have crashes but in kdepim-4.5.96-1.fc16.x86_64 kmail still shows mismatched items deleted and sometimes mismatched number of items in the inbox (i have 1 email but it says 2 are unread?)
Comment 3 Shawn Starr 2013-04-09 08:05:19 UTC
Close it, not an issue anymore and hasn't been for awhile