Bug 304281 - Konversation crash with LDAP auth over SSH tunnel
Summary: Konversation crash with LDAP auth over SSH tunnel
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.3.1
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-07-30 13:02 UTC by Jeffrey
Modified: 2018-10-27 02:28 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 Jeffrey 2012-07-30 13:02:43 UTC
Application: konversation (1.3.1)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 3.2.0-2-686-pae i686
Distribution: Debian GNU/Linux 6.0.5 (squeeze)

-- Information about the crash:
I created an SSH tunnel through my employer's gateway server:
ssh -X -t -t -t -l username -L 6697:irc.employer.com:6697  gateway.employer.com

and the SSH worked fine but LDAP Auth failed me.  I changed the Konversation Identity to one that my employer would know (my work's username) and when trying to connect, Konversation crashed.  Every time.

The crash can be reproduced every time.

 -- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
[KCrash Handler]
#6  QString::toLower (this=0x9e79b10) at tools/qstring.cpp:4793
#7  0x080f2e0e in Server::incoming (this=0x9dc7678) at ../../src/irc/server.cpp:1093
#8  0x080f591f in Server::qt_metacall (this=0x9dc7678, _c=QMetaObject::InvokeMetaMethod, _id=166173456, _a=0xbfbf798c) at ./server.moc:413
#9  0xb64c87aa in QMetaObject::metacall (object=0x9dc7678, cl=QMetaObject::InvokeMetaMethod, idx=91, argv=0xbfbf798c) at kernel/qmetaobject.cpp:237
#10 0xb64d71bb in QMetaObject::activate (sender=0xb21454c8, m=0xb682e464, local_signal_index=2, argv=0x0) at kernel/qobject.cpp:3295
#11 0xb67534c7 in KTcpSocket::readyRead (this=0xb21454c8) at ./ktcpsocket.moc:148
#12 0xb67575c6 in KTcpSocketPrivate::reemitReadyRead (this=0xb21454c8, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbfbf7adc) at ../../kdecore/network/ktcpsocket.cpp:353
#13 KTcpSocket::qt_metacall (this=0xb21454c8, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbfbf7adc) at ./ktcpsocket.moc:120
#14 0xb64c87aa in QMetaObject::metacall (object=0xb21454c8, cl=QMetaObject::InvokeMetaMethod, idx=22, argv=0xbfbf7adc) at kernel/qmetaobject.cpp:237
#15 0xb64d71bb in QMetaObject::activate (sender=0xb21801e8, m=0xb65d6dc8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#16 0xb65274c7 in QIODevice::readyRead (this=0xb21801e8) at .moc/release-shared/moc_qiodevice.cpp:91
#17 0xb69449c5 in QSslSocketBackendPrivate::transmit (this=0xb216d6f0) at ssl/qsslsocket_openssl.cpp:665
#18 0xb6939888 in QSslSocketPrivate::_q_readyReadSlot (this=0x9e79b10) at ssl/qsslsocket.cpp:2135
#19 0xb693d536 in QSslSocket::qt_metacall (this=0xb21801e8, _c=QMetaObject::InvokeMetaMethod, _id=39, _a=0xbfbf8d0c) at .moc/release-shared/moc_qsslsocket.cpp:121
#20 0xb64c87aa in QMetaObject::metacall (object=0xb21801e8, cl=QMetaObject::InvokeMetaMethod, idx=39, argv=0xbfbf8d0c) at kernel/qmetaobject.cpp:237
#21 0xb64d71bb in QMetaObject::activate (sender=0xb21ffde0, m=0xb65d6dc8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#22 0xb65274c7 in QIODevice::readyRead (this=0xb21ffde0) at .moc/release-shared/moc_qiodevice.cpp:91
#23 0xb6920a12 in QAbstractSocketPrivate::canReadNotification (this=0xb21ce408) at socket/qabstractsocket.cpp:639
#24 0xb690d97b in QAbstractSocketEngine::readNotification (this=0x9e52060) at socket/qabstractsocketengine.cpp:154
#25 0xb690ed43 in QReadNotifier::event (this=0x9e686b8, e=0xbfbf91c4) at socket/qnativesocketengine.cpp:1097
#26 0xb59945cc in QApplicationPrivate::notify_helper (this=0x9844538, receiver=0x9e23db0, e=0xbfbf91c4) at kernel/qapplication.cpp:4302
#27 0xb599b15e in QApplication::notify (this=0xbfbf9504, receiver=0x9e23db0, e=0xbfbf91c4) at kernel/qapplication.cpp:3706
#28 0xb6bdbbfa in KApplication::notify (this=0xbfbf9504, receiver=0x9e23db0, event=0xbfbf91c4) at ../../kdeui/kernel/kapplication.cpp:302
#29 0xb64c34cb in QCoreApplication::notifyInternal (this=0xbfbf9504, receiver=0x9e23db0, event=0xbfbf91c4) at kernel/qcoreapplication.cpp:726
#30 0xb64ef44a in QCoreApplication::sendEvent (source=0x9846710) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#31 socketNotifierSourceDispatch (source=0x9846710) at kernel/qeventdispatcher_glib.cpp:110
#32 0xb51ff305 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0xb5202fe8 in ?? () from /lib/libglib-2.0.so.0
#34 0xb52031c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0xb64ef075 in QEventDispatcherGlib::processEvents (this=0x9823318, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#36 0xb5a52ed5 in QGuiEventDispatcherGlib::processEvents (this=0x9823318, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#37 0xb64c1ae9 in QEventLoop::processEvents (this=0xbfbf9464, flags=) at kernel/qeventloop.cpp:149
#38 0xb64c1f3a in QEventLoop::exec (this=0xbfbf9464, flags=...) at kernel/qeventloop.cpp:201
#39 0xb64c716f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#40 0xb5994667 in QApplication::exec () at kernel/qapplication.cpp:3581
#41 0x080ab44a in main (argc=5, argv=0xbfbf9944) at ../../src/main.cpp:101

Reported using DrKonqi
Comment 1 Eike Hein 2012-07-30 14:36:38 UTC
Thanks for your report.

Devs: This maps to line 1268 in master's server.cpp.
Comment 3 Myriam Schweingruber 2013-04-13 14:25:30 UTC
What is the status of this, does it also apply to 1.5 RC1 or was this fixed already?
Comment 4 Andrew Crouthamel 2018-09-24 02:06:01 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 02:28:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!