Bug 263317

Summary: crash while reconnecting...
Product: [Applications] konversation Reporter: Mathieu Jobin <opensource>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED DUPLICATE    
Severity: crash CC: peter.simonsson
Priority: NOR    
Version: 1.3.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mathieu Jobin 2011-01-16 14:21:50 UTC
Application: konversation (1.3.1)
KDE Platform Version: 4.5.95 (4.6 RC2)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-24-generic i686
Distribution: Ubuntu 10.10

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

I had 4 server connection open. one SSL. I left konversation open over night. in the morning, I click on konversation in the taskbar. it was flashing due to a dialog window about reconnecting to the SSL server. I said I accepted the certificate, forever. and konversation crashed at that point.

maybe the connection to the server timeout before I could click on the dialog.

-- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
[KCrash Handler]
#7  0x00cf6299 in contains (this=0x9be4ed0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:863
#8  QSslSocketBackendPrivate::startHandshake (this=0x9be4ed0) at ssl/qsslsocket_openssl.cpp:1184
#9  0x00cf878d in QSslSocketBackendPrivate::transmit (this=0x9be4ed0) at ssl/qsslsocket_openssl.cpp:927
#10 0x00ceb2e8 in QSslSocketPrivate::_q_readyReadSlot (this=0x9e14568) at ssl/qsslsocket.cpp:2135
#11 0x00cf1996 in QSslSocket::qt_metacall (this=0x9b536d0, _c=QMetaObject::InvokeMetaMethod, _id=39, _a=0xbfe2b5bc) at .moc/release-shared/moc_qsslsocket.cpp:121
#12 0x05ddf8ca in QMetaObject::metacall (object=0x9b536d0, cl=165758312, idx=39, argv=0xbfe2b5bc) at kernel/qmetaobject.cpp:237
#13 0x05df26ad in QMetaObject::activate (sender=0x9df1200, m=0x5f0bc48, local_signal_index=0, argv=0x9e14568) at kernel/qobject.cpp:3280
#14 0x05e41ec7 in QIODevice::readyRead (this=0x9df1200) at .moc/release-shared/moc_qiodevice.cpp:91
#15 0x00cd1832 in QAbstractSocketPrivate::canReadNotification (this=0xa0377e0) at socket/qabstractsocket.cpp:639
#16 0x00cbdc5b in QAbstractSocketEngine::readNotification (this=0x9d1e858) at socket/qabstractsocketengine.cpp:154
#17 0x00cbf153 in QReadNotifier::event (this=0x45f1f00, e=0xbfe2ba74) at socket/qnativesocketengine.cpp:1103
#18 0x0451dfdc in QApplicationPrivate::notify_helper (this=0x9115458, receiver=0x98d6f60, e=0xbfe2ba74) at kernel/qapplication.cpp:4396
#19 0x0452404e in QApplication::notify (this=0xbfe2bdb4, receiver=0x98d6f60, e=0xbfe2ba74) at kernel/qapplication.cpp:3798
#20 0x011fff8a in KApplication::notify (this=0xbfe2bdb4, receiver=0x98d6f60, event=0xbfe2ba74) at ../../kdeui/kernel/kapplication.cpp:311
#21 0x05dd9b3b in QCoreApplication::notifyInternal (this=0xbfe2bdb4, receiver=0x98d6f60, event=0xbfe2ba74) at kernel/qcoreapplication.cpp:732
#22 0x05e0893a in sendEvent (source=0x91125b8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#23 socketNotifierSourceDispatch (source=0x91125b8) at kernel/qeventdispatcher_glib.cpp:110
#24 0x01a15855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x01a19668 in ?? () from /lib/libglib-2.0.so.0
#26 0x01a19848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x05e08565 in QEventDispatcherGlib::processEvents (this=0x910e4e0, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#28 0x045dfbe5 in QGuiEventDispatcherGlib::processEvents (this=0x910e4e0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x05dd8609 in QEventLoop::processEvents (this=0xbfe2bd14, flags=) at kernel/qeventloop.cpp:149
#30 0x05dd8a8a in QEventLoop::exec (this=0xbfe2bd14, flags=...) at kernel/qeventloop.cpp:201
#31 0x05ddd00f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#32 0x0451ce07 in QApplication::exec () at kernel/qapplication.cpp:3672
#33 0x080a87ca in _start ()

Reported using DrKonqi
Comment 1 Peter Simonsson 2011-01-16 16:34:15 UTC

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