Bug 301216 - Seg fault after not accepting invalid server certificate
Summary: Seg fault after not accepting invalid server certificate
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 13:26 UTC by ralph.smithen
Modified: 2013-04-10 13:27 UTC (History)
0 users

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 ralph.smithen 2012-06-05 13:26:41 UTC
Application: konversation (1.3.1 #4056.1)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic i686
Distribution: Linux Mint 12 Lisa

-- Information about the crash:
The power went to my router and so the wireless connection was severed while Konversation was running and connected to an IRC server. After the wireless came back up, the dialogue to enter credentials and re-establish the wireless link was showing, and I accepted.

Konversation then attempted to reconnect to the IRC service, and happened to get another server which had an invalid certificate (self-signed, I think). I normally click "Remember forever", but this time chose not to go back on the chat, so selected Cancel. The program then suffered a segmentation fault. That was the only connected IRC netword in Konversation at the time.

-- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
[KCrash Handler]
#7  0x00ea02f4 in QAbstractSocket::state (this=0x0) at socket/qabstractsocket.cpp:2568
#8  0x00ec8ba2 in QSslSocketBackendPrivate::transmit (this=0x8bbac90) at ssl/qsslsocket_openssl.cpp:1018
#9  0x00ebcba8 in QSslSocketPrivate::_q_readyReadSlot (this=0x8bbac90) at ssl/qsslsocket.cpp:2156
#10 0x00ec247f in QSslSocket::qt_metacall (this=0x88a46b0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfb0d304) at .moc/release-shared/moc_qsslsocket.cpp:121
#11 0x014cbb7d in metacall (argv=0xbfb0d304, idx=39, cl=QMetaObject::InvokeMetaMethod, object=0x88a46b0) at kernel/qmetaobject.cpp:237
#12 QMetaObject::metacall (object=0x88a46b0, cl=QMetaObject::InvokeMetaMethod, idx=39, argv=0xbfb0d304) at kernel/qmetaobject.cpp:232
#13 0x014daa6a in QMetaObject::activate (sender=0x89de278, m=0x15fbcd8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3278
#14 0x01527225 in QIODevice::readyRead (this=0x89de278) at .moc/release-shared/moc_qiodevice.cpp:91
#15 0x00ea3f9f in QAbstractSocketPrivate::canReadNotification (this=0x899c138) at socket/qabstractsocket.cpp:643
#16 0x00e90869 in QAbstractSocketEngine::readNotification (this=0x89fe928) at socket/qabstractsocketengine.cpp:154
#17 0x00e9148b in event (this=0x89afd90, e=<optimized out>) at socket/qnativesocketengine.cpp:1103
#18 QReadNotifier::event (this=0x89afd90, e=0xbfb0d684) at socket/qnativesocketengine.cpp:1100
#19 0x03169d84 in notify_helper (e=0xbfb0d684, receiver=0x89afd90, this=0x8505648) at kernel/qapplication.cpp:4486
#20 QApplicationPrivate::notify_helper (this=0x8505648, receiver=0x89afd90, e=0xbfb0d684) at kernel/qapplication.cpp:4458
#21 0x0316f133 in QApplication::notify (this=0xbfb0d684, receiver=0x89afd90, e=0xbfb0d684) at kernel/qapplication.cpp:3886
#22 0x0110c971 in KApplication::notify (this=0xbfb0d974, receiver=0x89afd90, event=0xbfb0d684) at ../../kdeui/kernel/kapplication.cpp:311
#23 0x014c519e in QCoreApplication::notifyInternal (this=0xbfb0d974, receiver=0x89afd90, event=0xbfb0d684) at kernel/qcoreapplication.cpp:787
#24 0x014f31d8 in sendEvent (event=0xbfb0d684, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#25 socketNotifierSourceDispatch (source=0x8507be8) at kernel/qeventdispatcher_glib.cpp:110
#26 0x0179825f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#27 0x01798990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#28 0x01798c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0x014f3ada in QEventDispatcherGlib::processEvents (this=0x84e0230, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#30 0x03221e7a in QGuiEventDispatcherGlib::processEvents (this=0x84e0230, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x014c41dd in QEventLoop::processEvents (this=0xbfb0d8d4, flags=...) at kernel/qeventloop.cpp:149
#32 0x014c4421 in QEventLoop::exec (this=0xbfb0d8d4, flags=...) at kernel/qeventloop.cpp:201
#33 0x014c919d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#34 0x03167924 in QApplication::exec () at kernel/qapplication.cpp:3760
#35 0x0807c0e2 in ?? ()
#36 0x054f9113 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#37 0x0807d3f9 in _start ()

Reported using DrKonqi
Comment 1 Myriam Schweingruber 2013-04-10 08:19:31 UTC
Is this still valid with Konversation 1.4 or 1.5 RC1?
Comment 2 ralph.smithen 2013-04-10 11:40:47 UTC
(In reply to comment #1)
> Is this still valid with Konversation 1.4 or 1.5 RC1?

I am now using Konversation 1.4. I've not seen the issue since, though I'm not sure whether the circumstances required to provoke it have been duplicated. Perhaps this should be closed if the behaviour's not been reported in newer versions.
Comment 3 Myriam Schweingruber 2013-04-10 13:27:55 UTC
Thank you for the fast feedback. I can't reproduce this with version 1.5 RC1 here, but feel free to reopen if this appears again in that or a later version.