Bug 277065 - Kmail Crashed after creating nested labels in GMAIL
Summary: Kmail Crashed after creating nested labels in GMAIL
Status: RESOLVED DUPLICATE of bug 153411
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-04 14:19 UTC by marko.gabriel.cz
Modified: 2011-12-07 18:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description marko.gabriel.cz 2011-07-04 14:19:08 UTC
Application: kmail (1.13.6)
KDE Platform Version: 4.6.4 (4.6.4)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:After reorganizing email in my Gmail account using nested labels via web interface i tried to refresh kmail. Crash happened immediately.
- Custom settings of the application:Gmail -> nested labels

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0xb775a780 (LWP 2242))]

Thread 3 (Thread 0xb4ce4b70 (LWP 2275)):
#0  0x00786416 in __kernel_vsyscall ()
#1  0x006c9f76 in __poll (fds=0x94f1a50, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0x054d184b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x054c11af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x054c192b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x04390304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0x054ea2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x01093e99 in start_thread (arg=0xb4ce4b70) at pthread_create.c:304
#8  0x006d873e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb574fb70 (LWP 2364)):
#0  0x054c103c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0x054c1524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x06de5577 in QEventDispatcherGlib::processEvents (this=0x9b442d8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#3  0x06db7289 in QEventLoop::processEvents (this=0xb574f220, flags=...) at kernel/qeventloop.cpp:149
#4  0x06db7522 in QEventLoop::exec (this=0xb574f220, flags=...) at kernel/qeventloop.cpp:201
#5  0x06cc12a0 in QThread::exec (this=0x9b42a38) at thread/qthread.cpp:492
#6  0x06d98fdb in QInotifyFileSystemWatcherEngine::run (this=0x9b42a38) at io/qfilesystemwatcher_inotify.cpp:248
#7  0x06cc3da2 in QThreadPrivate::start (arg=0x9b42a38) at thread/qthread_unix.cpp:320
#8  0x01093e99 in start_thread (arg=0xb574fb70) at pthread_create.c:304
#9  0x006d873e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb775a780 (LWP 2242)):
[KCrash Handler]
#7  0x00d83177 in KMail::ISubject::notify (this=0x9807f10) at ../../kmail/isubject.cpp:33
#8  0x00a97cd4 in KMMessage::updateBodyPart (this=0x9807ea0, partSpecifier=..., data=...) at ../../kmail/kmmessage.cpp:3185
#9  0x00d5b512 in KMail::ImapJob::slotGetMessageResult (this=0x98b8a20, job=0x9ea26c0) at ../../kmail/imapjob.cpp:435
#10 0x00d5fb7f in KMail::ImapJob::qt_metacall (this=0x98b8a20, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfe47638) at ./imapjob.moc:88
#11 0x06dbe6ba in QMetaObject::metacall (object=0x98b8a20, cl=QMetaObject::InvokeMetaMethod, idx=12, argv=0xbfe47638) at kernel/qmetaobject.cpp:237
#12 0x06dce4ff in QMetaObject::activate (sender=0x9ea26c0, m=0x9f0548, local_signal_index=3, argv=0xbfe47638) at kernel/qobject.cpp:3287
#13 0x0089be93 in KJob::result (this=0x9ea26c0, _t1=0x9ea26c0) at ./kjob.moc:194
#14 0x0089bee8 in KJob::emitResult (this=0x9ea26c0) at ../../kdecore/jobs/kjob.cpp:312
#15 0x012e8bbb in KIO::SimpleJob::slotFinished (this=0x9ea26c0) at ../../kio/kio/job.cpp:525
#16 0x012ee5c6 in KIO::TransferJob::slotFinished (this=0x9ea26c0) at ../../kio/kio/job.cpp:1113
#17 0x012f1fb3 in KIO::TransferJob::qt_metacall (this=0x9ea26c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfe478dc) at ./jobclasses.moc:367
#18 0x06dbe6ba in QMetaObject::metacall (object=0x9ea26c0, cl=QMetaObject::InvokeMetaMethod, idx=47, argv=0xbfe478dc) at kernel/qmetaobject.cpp:237
#19 0x06dce4ff in QMetaObject::activate (sender=0x9cbf180, m=0x146d6c4, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3287
#20 0x013987f7 in KIO::SlaveInterface::finished (this=0x9cbf180) at ./slaveinterface.moc:171
#21 0x0139b627 in KIO::SlaveInterface::dispatch (this=0x9cbf180, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:173
#22 0x013980a3 in KIO::SlaveInterface::dispatch (this=0x9cbf180) at ../../kio/kio/slaveinterface.cpp:89
#23 0x0138a7e8 in KIO::Slave::gotInput (this=0x9cbf180) at ../../kio/kio/slave.cpp:348
#24 0x0138af13 in KIO::Slave::qt_metacall (this=0x9cbf180, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfe47bec) at ./slave.moc:82
#25 0x06dbe6ba in QMetaObject::metacall (object=0x9cbf180, cl=QMetaObject::InvokeMetaMethod, idx=30, argv=0xbfe47bec) at kernel/qmetaobject.cpp:237
#26 0x06dce4ff in QMetaObject::activate (sender=0x9b66758, m=0x146a440, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3287
#27 0x012b57a7 in KIO::Connection::readyRead (this=0x9b66758) at ./connection.moc:92
#28 0x012b5fc6 in KIO::ConnectionPrivate::dequeue (this=0x985edd0) at ../../kio/kio/connection.cpp:82
#29 0x012b6076 in KIO::Connection::qt_metacall (this=0x9b66758, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x9f09c00) at ./connection.moc:79
#30 0x06dbe6ba in QMetaObject::metacall (object=0x9b66758, cl=QMetaObject::InvokeMetaMethod, idx=5, argv=0x9f09c00) at kernel/qmetaobject.cpp:237
#31 0x06dc8e16 in QMetaCallEvent::placeMetaCall (this=0x95f0d40, object=0x9b66758) at kernel/qobject.cpp:535
#32 0x06dcd3b7 in QObject::event (this=0x9b66758, e=0x95f0d40) at kernel/qobject.cpp:1226
#33 0x05788d24 in QApplicationPrivate::notify_helper (this=0x9377490, receiver=0x9b66758, e=0x95f0d40) at kernel/qapplication.cpp:4462
#34 0x0578d8ce in QApplication::notify (this=0xbfe4859c, receiver=0x9b66758, e=0x95f0d40) at kernel/qapplication.cpp:3862
#35 0x0042336a in KApplication::notify (this=0xbfe4859c, receiver=0x9b66758, event=0x95f0d40) at ../../kdeui/kernel/kapplication.cpp:311
#36 0x06db80bb in QCoreApplication::notifyInternal (this=0xbfe4859c, receiver=0x9b66758, event=0x95f0d40) at kernel/qcoreapplication.cpp:731
#37 0x06dbbc79 in sendEvent (receiver=0x0, event_type=0, data=0x930af40) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#38 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x930af40) at kernel/qcoreapplication.cpp:1372
#39 0x06dbbe0d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1265
#40 0x06de53c4 in sendPostedEvents (s=0x9379690) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#41 postEventSourceDispatch (s=0x9379690) at kernel/qeventdispatcher_glib.cpp:277
#42 0x054c0aa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#43 0x054c1270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#44 0x054c1524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#45 0x06de553c in QEventDispatcherGlib::processEvents (this=0x930aa98, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#46 0x0583c775 in QGuiEventDispatcherGlib::processEvents (this=0x930aa98, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#47 0x06db7289 in QEventLoop::processEvents (this=0xbfe48464, flags=...) at kernel/qeventloop.cpp:149
#48 0x06db7522 in QEventLoop::exec (this=0xbfe48464, flags=...) at kernel/qeventloop.cpp:201
#49 0x06dbbecc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#50 0x057868e7 in QApplication::exec () at kernel/qapplication.cpp:3736
#51 0x0804a733 in main (argc=0, argv=0x0) at ../../kmail/main.cpp:158

Possible duplicates by query: bug 276031, bug 275882, bug 275239, bug 274259, bug 273179.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-07-08 08:50:32 UTC

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