Bug 223711 - crash after changing network after suspend
Summary: crash after changing network after suspend
Status: RESOLVED DUPLICATE of bug 193514
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-21 21:44 UTC by Jonas
Modified: 2010-01-22 01:07 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 Jonas 2010-01-21 21:44:09 UTC
Application that crashed: kontact
Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4) "release 2"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.8-0.1-default x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
How to reproduce:

Log in to network 1 -> suspend laptop to ram -> start again -> connect to network 2 -> kmail is now not able to check mails (IMAP) -> close kontact -> start it again and it craches

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  Kontact::MainWindow::activatePluginModule (this=0x6c63e0) at /usr/src/debug/kdepim-4.3.4/kontact/src/mainwindow.cpp:303
#6  0x0000000000404792 in KontactApp::newInstance (this=0x7fffc0708bc0) at /usr/src/debug/kdepim-4.3.4/kontact/src/main.cpp:147
#7  0x00007faf33ff5c46 in KUniqueApplicationAdaptor::newInstance (this=0x6c9ff0, asn_id=<value optimized out>, args=...) at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kuniqueapplication.cpp:459
#8  0x00007faf33ff6236 in KUniqueApplicationAdaptor::qt_metacall (this=0x6c9ff0, _c=InvokeMetaMethod, _id=9874592, _a=0x7fffc0707ef0)
    at /usr/src/debug/kdelibs-4.3.4/build/kdeui/kuniqueapplication_p.moc:75
#9  0x00007faf30c45b78 in ?? () from /usr/lib64/libQtDBus.so.4
#10 0x00007faf30c469b3 in ?? () from /usr/lib64/libQtDBus.so.4
#11 0x00007faf30c47237 in ?? () from /usr/lib64/libQtDBus.so.4
#12 0x00007faf30c474b8 in ?? () from /usr/lib64/libQtDBus.so.4
#13 0x00007faf336802d9 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#14 0x00007faf32b45efd in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007faf32b3c2ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007faf32b4357e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007faf33feef26 in KApplication::notify (this=0x7fffc0708bc0, receiver=0x7fffc0708bc0, event=0x1a12660) at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#18 0x00007faf33670ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007faf336719ea in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#20 0x00007faf33699803 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007faf2c270dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007faf2c2747a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007faf2c2748d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007faf336993a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007faf32bcf31e in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007faf3366f712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007faf3366fae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007faf33671c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#29 0x0000000000403f67 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.3.4/kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 213012

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-21 23:15:05 UTC
You already posted this info to bug 193514. Regards

*** This bug has been marked as a duplicate of bug 193514 ***
Comment 2 Jonas 2010-01-22 00:12:06 UTC
sorry for that but DrKonqi needed nearly 3 Minutes to post this bug
Comment 3 Dario Andres 2010-01-22 01:07:33 UTC
This site is slow sometimes.. so it may be possible.
Regards