Bug 243283 - Crash during tab completion (Channel::completeNick, Nick::getChannelNick)
Summary: Crash during tab completion (Channel::completeNick, Nick::getChannelNick)
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: tabcompletion (show other bugs)
Version: 1.2.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-06-30 21:05 UTC by Josh
Modified: 2018-10-27 04:17 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 Josh 2010-06-30 21:05:21 UTC
Application: konversation (1.2.3)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
Randomly crashed when trying to tab a username.

[Ad-TAB- (Crashed)

The crash does not seem to be reproducible.

 -- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
[KCrash Handler]
#6  KSharedPtr (this=0x124) at /usr/include/ksharedptr.h:84
#7  Nick::getChannelNick (this=0x124) at ../../src/irc/nick.cpp:51
#8  0x08102943 in Channel::completeNick (this=0x9aa0e78) at ../../src/irc/channel.cpp:878
#9  0x0810cc02 in Channel::qt_metacall (this=0x9aa0e78, _c=QMetaObject::InvokeMetaMethod, _id=76, _a=0xbfcab26c) at ./channel.moc:190
#10 0x0200cc9a in QMetaObject::metacall (object=0x9aa0e78, cl=4294967287, idx=76, argv=0xbfcab26c) at kernel/qmetaobject.cpp:237
#11 0x0201b3d5 in QMetaObject::activate (sender=0x9b2c290, m=0x827185c, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#12 0x08171b39 in IRCInput::nickCompletion (this=0x9b2c290) at ./ircinput.moc:129
#13 0x081736a0 in IRCInput::keyPressEvent (this=0x9b2c290, e=0xbfcabaf4) at ../../src/viewer/ircinput.cpp:231
#14 0x0242e503 in QWidget::event (this=0x9b2c290, event=0xbfcabaf4) at kernel/qwidget.cpp:8033
#15 0x0282afd3 in QFrame::event (this=0x9b2c290, e=0xbfcabaf4) at widgets/qframe.cpp:557
#16 0x028c5d97 in QAbstractScrollArea::event (this=0x9b2c290, e=0xbfcabaf4) at widgets/qabstractscrollarea.cpp:989
#17 0x028aef4d in QTextEdit::event (this=0x9b2c290, e=0xbfcabaf4) at widgets/qtextedit.cpp:1070
#18 0x08eeae73 in KTextEdit::event (this=0x9b2c290, ev=0xbfcabaf4) at ../../kdeui/widgets/ktextedit.cpp:327
#19 0x08171cd2 in IRCInput::event (this=0x9b2c290, e=0xbfcabaf4) at ../../src/viewer/ircinput.cpp:323
#20 0x023d04dc in QApplicationPrivate::notify_helper (this=0x95b3af8, receiver=0x9b2c290, e=0xbfcabaf4) at kernel/qapplication.cpp:4300
#21 0x023d8b71 in QApplication::notify (this=0xbfcac554, receiver=0x9b2c290, e=0xbfcabaf4) at kernel/qapplication.cpp:3763
#22 0x08dccf2a in KApplication::notify (this=0xbfcac554, receiver=0x9b2c290, event=0xbfcabaf4) at ../../kdeui/kernel/kapplication.cpp:302
#23 0x02007a3b in QCoreApplication::notifyInternal (this=0xbfcac554, receiver=0x9b2c290, event=0xbfcabaf4) at kernel/qcoreapplication.cpp:704
#24 0x023d12be in QCoreApplication::sendSpontaneousEvent (receiver=0x9b2c290, event=0x124) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#25 qt_sendSpontaneousEvent (receiver=0x9b2c290, event=0x124) at kernel/qapplication.cpp:5279
#26 0x0248ad90 in QKeyMapper::sendKeyEvent (keyWidget=0x9b2c290, grab=false, type=QEvent::KeyPress, code=16777217, modifiers=..., text=..., autorepeat=<value optimized out>, 
    count=<value optimized out>, nativeScanCode=23, nativeVirtualKey=65289, nativeModifiers=0) at kernel/qkeymapper_x11.cpp:1861
#27 0x0248d2f5 in QKeyMapperPrivate::translateKeyEvent (this=0x95dbfd0, keyWidget=0x9b2c290, event=0xbfcac1bc, grab=40) at kernel/qkeymapper_x11.cpp:1831
#28 0x02460757 in QApplication::x11ProcessEvent (this=0xbfcac554, event=0xbfcac1bc) at kernel/qapplication_x11.cpp:3394
#29 0x0249060a in x11EventSourceDispatch (s=0x95b84a8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#30 0x0789e5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#31 0x078a22d8 in ?? () from /lib/libglib-2.0.so.0
#32 0x078a24b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#33 0x020335d5 in QEventDispatcherGlib::processEvents (this=0x9592a60, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#34 0x02490135 in QGuiEventDispatcherGlib::processEvents (this=0x9592a60, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#35 0x02006059 in QEventLoop::processEvents (this=0xbfcac4b4, flags=) at kernel/qeventloop.cpp:149
#36 0x020064aa in QEventLoop::exec (this=0xbfcac4b4, flags=...) at kernel/qeventloop.cpp:201
#37 0x0200a69f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#38 0x023d0577 in QApplication::exec () at kernel/qapplication.cpp:3579
#39 0x080a7148 in main (argc=5, argv=0xbfcac984) at ../../src/main.cpp:100

Reported using DrKonqi
Comment 1 Eike Hein 2011-06-27 13:22:30 UTC
Renamed for clarity.
Comment 2 Myriam Schweingruber 2013-04-14 00:54:30 UTC
Is this still reproducible with Konversation 1.4 or 1.5 RC1? Then we would need
a new backtrace.
Comment 3 Andrew Crouthamel 2018-09-24 02:02:19 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 4 Andrew Crouthamel 2018-10-27 04:17:12 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!