Bug 250047 - kontact crashed while searching for a recipient
Summary: kontact crashed while searching for a recipient
Status: RESOLVED DUPLICATE of bug 190617
Alias: None
Product: kmail
Classification: Applications
Component: addressbook (show other bugs)
Version: 1.13.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-03 17:19 UTC by Michael Brach
Modified: 2011-04-24 22:21 UTC (History)
3 users (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 Michael Brach 2010-09-03 17:19:09 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-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
After typing some letters into the "To:" field of the mail editor, Kontact was searching for an email address (animated hourglass as mouse pointer). For it did not stop, I closed Kontact, but instead of closing, it crashed.

The crash can be reproduced some of the time.

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

Thread 2 (Thread 0x7f606b331710 (LWP 2497)):
#0  0x00007f6081474430 in ?? () from /lib/libglib-2.0.so.0
#1  0x00007f60814748fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#2  0x00007f6089d2b566 in QEventDispatcherGlib::processEvents (this=0x2172e20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#3  0x00007f6089d00992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#4  0x00007f6089d00d6c in QEventLoop::exec (this=0x7f606b330d90, flags=) at kernel/qeventloop.cpp:201
#5  0x00007f6089c0ad59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#6  0x00007f6089ce1178 in QInotifyFileSystemWatcherEngine::run (this=0x27b6300) at io/qfilesystemwatcher_inotify.cpp:248
#7  0x00007f6089c0d775 in QThreadPrivate::start (arg=0x27b6300) at thread/qthread_unix.cpp:248
#8  0x00007f60839eb9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#9  0x00007f608894c6fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f608b86a780 (LWP 2422)):
[KCrash Handler]
#5  0x0000000000000000 in ?? ()
#6  0x00007f608b195598 in KPIM::AddresseeLineEdit::doCompletion (this=0x4100000, ctrlT=false) at ../../libkdepim/addresseelineedit.cpp:456
#7  0x00007f608b19a734 in KPIM::AddresseeLineEdit::qt_metacall (this=0x4100000, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff475dde10) at ./addresseelineedit.moc:97
#8  0x00007f6070ed6478 in KMLineEdit::qt_metacall (this=0x4100000, _c=1197333520, _id=0, _a=0x0) at ./kmlineeditspell.moc:74
#9  0x00007f6070f44908 in RecipientLineEdit::qt_metacall (this=0x4100000, _c=1197333520, _id=0, _a=0x0) at ./recipientseditor.moc:135
#10 0x00007f6089d14e3f in QMetaObject::activate (sender=0x4100000, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293
#11 0x00007f608a7b8a25 in KLineEdit::completion (this=0x4100000, _t1=<value optimized out>) at ./klineedit.moc:233
#12 0x00007f608a7b8b6b in KLineEdit::doCompletion (this=0x4100000, txt=...) at ../../kdeui/widgets/klineedit.cpp:1769
#13 0x00007f608a7bcbae in KLineEdit::keyPressEvent (this=0x4100000, e=0x7fff475debd0) at ../../kdeui/widgets/klineedit.cpp:926
#14 0x00007f608b198e25 in KPIM::AddresseeLineEdit::keyPressEvent (this=0x4100000, e=0x7fff475debd0) at ../../libkdepim/addresseelineedit.cpp:233
#15 0x00007f6070f460d1 in RecipientLineEdit::keyPressEvent (this=0x4100000, ev=0x7fff475debd0) at ../../kmail/recipientseditor.cpp:144
#16 0x00007f608911122e in QWidget::event (this=0x4100000, event=0x7fff475debd0) at kernel/qwidget.cpp:8033
#17 0x00007f60894c6ce3 in QLineEdit::event (this=0x4100000, e=0x7fff475debd0) at widgets/qlineedit.cpp:1474
#18 0x00007f608a7bddca in KLineEdit::event (this=0x4100000, ev=0x7fff475debd0) at ../../kdeui/widgets/klineedit.cpp:1329
#19 0x00007f60890bb22c in QApplicationPrivate::notify_helper (this=0x16552a0, receiver=0x4100000, e=0x7fff475debd0) at kernel/qapplication.cpp:4300
#20 0x00007f60890c2ec5 in QApplication::notify (this=<value optimized out>, receiver=0x4100000, e=0x7fff475debd0) at kernel/qapplication.cpp:3763
#21 0x00007f608a6ea526 in KApplication::notify (this=0x7fff475dfb90, receiver=0x4100000, event=0x7fff475debd0) at ../../kdeui/kernel/kapplication.cpp:302
#22 0x00007f6089d0206c in QCoreApplication::notifyInternal (this=0x7fff475dfb90, receiver=0x4100000, event=0x7fff475debd0) at kernel/qcoreapplication.cpp:704
#23 0x00007f608916616a in QKeyMapper::sendKeyEvent (keyWidget=0x4100000, grab=<value optimized out>, type=QEvent::KeyPress, code=82, modifiers=<value optimized out>, text=..., autorepeat=false, 
    count=1, nativeScanCode=27, nativeVirtualKey=114, nativeModifiers=0) at kernel/qkeymapper_x11.cpp:1861
#24 0x00007f60891686f0 in QKeyMapperPrivate::translateKeyEvent (this=0x16919e0, keyWidget=0x4100000, event=<value optimized out>, grab=16) at kernel/qkeymapper_x11.cpp:1831
#25 0x00007f608913f904 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff475df7a0) at kernel/qapplication_x11.cpp:3394
#26 0x00007f608916b882 in x11EventSourceDispatch (s=0x1656520, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#27 0x00007f60814708c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#28 0x00007f6081474748 in ?? () from /lib/libglib-2.0.so.0
#29 0x00007f60814748fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#30 0x00007f6089d2b513 in QEventDispatcherGlib::processEvents (this=0x161a990, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#31 0x00007f608916b46e in QGuiEventDispatcherGlib::processEvents (this=0x4100000, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007f6089d00992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#33 0x00007f6089d00d6c in QEventLoop::exec (this=0x7fff475dfad0, flags=) at kernel/qeventloop.cpp:201
#34 0x00007f6089d04aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#35 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 190617.

Possible duplicates by query: bug 249834, bug 249539, bug 245365, bug 245187, bug 243461.

Reported using DrKonqi
Comment 1 Michael Brach 2010-09-16 10:21:09 UTC
This bug happens all the time, if I am not cautious. This is my workaround:


1. Don't edit an email (for kontact would hang / crash while searching/completing  email addresses -- see bug report)
2. Wait until the Akonadi list of status and error messages appears (especially "no resorce found" will show up)
3. Open Akonadi server configuration (KDE menu)
4. Stop and then restart Akonadi server
5. Click on "test"
6. no error is in the list
7. Edit and send email as you wish to
Comment 2 Ariel Garcia 2010-12-01 16:49:46 UTC
Probably duplicate of Bug#248541 (https://bugs.kde.org/show_bug.cgi?id=248541)
Comment 3 Unknown 2010-12-01 23:18:52 UTC
I am not sure this is a duplicate of my bug (https://bugs.kde.org/show_bug.cgi?id=248541) as the OP of this bug mentioned that kontact is searching for adddreses and seems to still be alive.  My bug mentioned a total freeze or hang of the interface that requires kill or terminated via KDE.
Comment 4 Michael Brach 2010-12-02 00:22:22 UTC
Dear Louis-Philippe. Perhaps I (the reporter) was not precise: Kmail would hang and freeze as in your bug, therefore I had to stop Kmail. Thus both reports could contain the same bug. Are you able to verify my workaround as laid down in  https://bugs.kde.org/show_bug.cgi?id=248541 ?
Comment 5 Unknown 2010-12-08 02:01:13 UTC
Michael,  I could not reproduce your workaround...  I tried to perform the steps you described and it ended up in the same spot....  Do you have other ideas?
Comment 6 Christophe Marin 2011-04-24 22:21:46 UTC

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