Bug 234138 - Kontact crashed after clicking "Check Mail" button.
Summary: Kontact crashed after clicking "Check Mail" button.
Status: RESOLVED FIXED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 234200 236460 241836 247939 248697 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-12 09:57 UTC by cscupples
Modified: 2010-09-30 11:27 UTC (History)
5 users (show)

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 cscupples 2010-04-12 09:57:29 UTC
Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-20-generic x86_64
Distribution: Ubuntu lucid (development branch)

-- Information about the crash:
Kontact segfaulted after I clicked upon the "Check Mail" button, and it seems to be doing so /very/ consistently. That's all there is to it.

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f3791cf7710 (LWP 7873)):
#0  0x00007f37b2496f93 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f37aafcc4a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f37aafcc8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f37b3881566 in QEventDispatcherGlib::processEvents (this=0x1f41ad0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f37b3856992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f37b3856d6c in QEventLoop::exec (this=0x7f3791cf6d90, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f37b3760d59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007f37b3837178 in QInotifyFileSystemWatcherEngine::run (this=0x1f40ef0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f37b3763775 in QThreadPrivate::start (arg=0x1f40ef0) at thread/qthread_unix.cpp:248
#9  0x00007f37ad5429ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007f37b24a36dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f37b53c9780 (LWP 7857)):
[KCrash Handler]
#5  QBasicAtomicInt::deref (this=0x2af9e10, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:133
#6  QString::operator= (this=0x2af9e10, other=...) at tools/qstring.cpp:1281
#7  0x00007f37b4d06add in KPIM::ProgressItem::setStatus (this=0x2af9df0, v=...) at ../../libkdepim/progressmanager.cpp:118
#8  0x00007f379b6e828d in KMail::PopAccount::slotData (this=0x183deb0, job=<value optimized out>, data=<value optimized out>) at ../../kmail/popaccount.cpp:962
#9  0x00007f379b6e9329 in KMail::PopAccount::qt_metacall (this=0x183deb0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc62f09e0) at ./popaccount.moc:91
#10 0x00007f37b386ae3f in QMetaObject::activate (sender=0x1bcc120, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffffff7adb8) at kernel/qobject.cpp:3293
#11 0x00007f37b0feac34 in KIO::TransferJob::data (this=0x2af9e10, _t1=0x1bcc120, _t2=<value optimized out>) at ./jobclasses.moc:388
#12 0x00007f37b0fed450 in KIO::TransferJob::slotData (this=0x1bcc120, _data=...) at ../../kio/kio/job.cpp:953
#13 0x00007f37b0ff0b16 in KIO::TransferJob::qt_metacall (this=0x1bcc120, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc62f0bc0) at ./jobclasses.moc:368
#14 0x00007f37b386ae3f in QMetaObject::activate (sender=0x2a865d0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffffff7adb8) at kernel/qobject.cpp:3293
#15 0x00007f37b10af332 in KIO::SlaveInterface::data (this=0x2af9e10, _t1=<value optimized out>) at ./slaveinterface.moc:146
#16 0x00007f37b10b2320 in KIO::SlaveInterface::dispatch (this=0x2a865d0, _cmd=100, rawdata=...) at ../../kio/kio/slaveinterface.cpp:163
#17 0x00007f37b10af5e3 in KIO::SlaveInterface::dispatch (this=0x2a865d0) at ../../kio/kio/slaveinterface.cpp:91
#18 0x00007f37b10a3a46 in KIO::Slave::gotInput (this=0x2a865d0) at ../../kio/kio/slave.cpp:324
#19 0x00007f37b10a3c2c in KIO::Slave::qt_metacall (this=0x2a865d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc62f0fb0) at ./slave.moc:82
#20 0x00007f37b386ae3f in QMetaObject::activate (sender=0x199a4f0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffffff7adb8) at kernel/qobject.cpp:3293
#21 0x00007f37b0fc19d7 in KIO::ConnectionPrivate::dequeue (this=0x2afa300) at ../../kio/kio/connection.cpp:82
#22 0x00007f37b0fc1afd in KIO::Connection::qt_metacall (this=0x199a4f0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x2acc1d0) at ./connection.moc:79
#23 0x00007f37b3867d49 in QObject::event (this=0x199a4f0, e=0x2b03480) at kernel/qobject.cpp:1248
#24 0x00007f37b2c1122c in QApplicationPrivate::notify_helper (this=0x14e9a40, receiver=0x199a4f0, e=0x2b03480) at kernel/qapplication.cpp:4300
#25 0x00007f37b2c176fb in QApplication::notify (this=0x7fffc62f1ac0, receiver=0x199a4f0, e=0x2b03480) at kernel/qapplication.cpp:4183
#26 0x00007f37b4240526 in KApplication::notify (this=0x7fffc62f1ac0, receiver=0x199a4f0, event=0x2b03480) at ../../kdeui/kernel/kapplication.cpp:302
#27 0x00007f37b385806c in QCoreApplication::notifyInternal (this=0x7fffc62f1ac0, receiver=0x199a4f0, event=0x2b03480) at kernel/qcoreapplication.cpp:704
#28 0x00007f37b385a7e7 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x14c0620) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x14c0620) at kernel/qcoreapplication.cpp:1345
#30 0x00007f37b38819d3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#31 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#32 0x00007f37aafc88c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0x00007f37aafcc748 in ?? () from /lib/libglib-2.0.so.0
#34 0x00007f37aafcc8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0x00007f37b3881513 in QEventDispatcherGlib::processEvents (this=0x14bfd70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#36 0x00007f37b2cc146e in QGuiEventDispatcherGlib::processEvents (this=0x2af9e10, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x00007f37b3856992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#38 0x00007f37b3856d6c in QEventLoop::exec (this=0x7fffc62f1a00, flags=) at kernel/qeventloop.cpp:201
#39 0x00007f37b385aaab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#40 0x0000000000403e8e in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:224

This bug may be a duplicate of or related to bug 191677.

Possible duplicates by query: bug 227210, bug 216892, bug 207996, bug 201436.

Reported using DrKonqi
Comment 1 cscupples 2010-04-12 10:05:49 UTC
After checking the names of my POP3 accounts, I found that they shared the same name, and by fixing that, the bug went away. 

A possible solution, from a dev standpoint, to prevent this is to have the default name of the Mail accounts be filled in automatically, after the user inputs his/her server information. At the very least, a system to check whether that account name exists yet would prevent any further cases from appearing.
Comment 2 Christophe Marin 2010-06-07 00:03:17 UTC
*** Bug 236460 has been marked as a duplicate of this bug. ***
Comment 3 Nicolas L. 2010-06-16 01:01:22 UTC
*** Bug 234200 has been marked as a duplicate of this bug. ***
Comment 4 Nicolas L. 2010-06-16 01:01:31 UTC
*** Bug 241836 has been marked as a duplicate of this bug. ***
Comment 5 Nicolas L. 2010-08-15 11:45:45 UTC
*** Bug 247939 has been marked as a duplicate of this bug. ***
Comment 6 Nicolas L. 2010-08-22 14:18:24 UTC
*** Bug 248697 has been marked as a duplicate of this bug. ***
Comment 7 Laurent Montel 2010-09-30 11:27:28 UTC
I made a fix in kmail-4.4.x I think that it fixes this crash.
Reopen it if you have still this crash