Bug 248192

Summary: Konversation crash when closing tab
Product: [Applications] konversation Reporter: Jonas Thiem <contact>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED WORKSFORME    
Severity: crash CC: hein
Priority: NOR Keywords: triaged
Version: 1.3.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jonas Thiem 2010-08-18 00:15:04 UTC
Application: konversation (1.3.1)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.33.6-147.2.4.fc13.i686.PAE i686
Distribution: "Fedora release 13 (Goddard)"

-- Information about the crash:
I just had started some memory intensive application (LMMS) and when firing up Konversation with all servers in the server list, I decided (while Konversation was just about to connect to the 8+ servers) that I would disconnect some of them and clicked the top most tab and closed it (I think I used CTRL+W rather than the context menu). This triggered a crash.

 -- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
[KCrash Handler]
#6  0x08176fe3 in KSharedPtr (this=0x9124790) at /usr/include/kde4/ksharedptr.h:84
#7  serverGroup (this=0x9124790) at /usr/src/debug/konversation-1.3.1/src/connectionsettings.h:34
#8  getServerGroup (this=0x9124790) at /usr/src/debug/konversation-1.3.1/src/irc/server.h:100
#9  StatusPanel::getChannelEncoding (this=0x9124790) at /usr/src/debug/konversation-1.3.1/src/viewer/statuspanel.cpp:314
#10 0x0817b857 in ViewContainer::updateViewEncoding (this=0x8dd75f0, view=0x9124790) at /usr/src/debug/konversation-1.3.1/src/viewer/viewcontainer.cpp:1712
#11 0x08180fd6 in ViewContainer::showViewContextMenu (this=0x8dd75f0, tab=0x9124790, pos=...) at /usr/src/debug/konversation-1.3.1/src/viewer/viewcontainer.cpp:1805
#12 0x08182e90 in ViewContainer::qt_metacall (this=0x8dd75f0, _c=QMetaObject::InvokeMetaMethod, _id=45, _a=0xbfc622f4)
    at /usr/src/debug/konversation-1.3.1/i686-redhat-linux-gnu/src/viewcontainer.moc:329
#13 0x023608ab in QMetaObject::metacall (object=0x8dd75f0, cl=QMetaObject::InvokeMetaMethod, idx=49, argv=0xbfc622f4) at kernel/qmetaobject.cpp:237
#14 0x0236f755 in QMetaObject::activate (sender=0x8dd12e8, m=0x8257eb8, local_signal_index=3, argv=0xbfc622f4) at kernel/qobject.cpp:3295
#15 0x081836ec in ViewTree::showViewContextMenu (this=0x8dd12e8, _t1=0x9124790, _t2=...) at /usr/src/debug/konversation-1.3.1/i686-redhat-linux-gnu/src/viewtree.moc:142
#16 0x081846af in ViewTree::contentsContextMenuEvent (this=0x8dd12e8, e=0xbfc62384) at /usr/src/debug/konversation-1.3.1/src/viewer/viewtree.cpp:650
#17 0x00f193ed in Q3ScrollView::viewportContextMenuEvent(QContextMenuEvent*) () from /usr/lib/libQt3Support.so.4
#18 0x00f1b429 in Q3ScrollView::eventFilter(QObject*, QEvent*) () from /usr/lib/libQt3Support.so.4
#19 0x00ec127b in Q3ListView::eventFilter(QObject*, QEvent*) () from /usr/lib/libQt3Support.so.4
#20 0x0235b04a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x8b41830, receiver=0x8dd1b30, event=0xbfc629a8) at kernel/qcoreapplication.cpp:841
#21 0x011c8bba in QApplicationPrivate::notify_helper (this=0x8b41830, receiver=0x8dd1b30, e=0xbfc629a8) at kernel/qapplication.cpp:4302
#22 0x011cfa34 in QApplication::notify (this=0xbfc63234, receiver=0x8dd1b30, e=0xbfc629a8) at kernel/qapplication.cpp:3950
#23 0x0853500b in KApplication::notify (this=0xbfc63234, receiver=0x8dd1b30, event=0xbfc629a8) at /usr/src/debug/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302
#24 0x0235be13 in QCoreApplication::notifyInternal (this=0xbfc63234, receiver=0x8dd1b30, event=0xbfc629a8) at kernel/qcoreapplication.cpp:726
#25 0x012520af in QCoreApplication::sendSpontaneousEvent (receiver=0x8dd1b30, event=0xbfc629a8) at ../../src/corelib/kernel/qcoreapplication.h:218
#26 0x0124c7bc in QETWidget::translateMouseEvent (this=0x8dd76b0, event=0xbfc62e9c) at kernel/qapplication_x11.cpp:4385
#27 0x0124bba3 in QApplication::x11ProcessEvent (this=0xbfc63234, event=0xbfc62e9c) at kernel/qapplication_x11.cpp:3391
#28 0x01277baa in x11EventSourceDispatch (s=0x8b47c40, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#29 0x08a3e525 in g_main_dispatch (context=0x8b46e90) at gmain.c:1960
#30 IA__g_main_context_dispatch (context=0x8b46e90) at gmain.c:2513
#31 0x08a42268 in g_main_context_iterate (context=0x44e490, block=1, dispatch=1, self=0x8b42db8) at gmain.c:2591
#32 0x08a42449 in IA__g_main_context_iteration (context=0x8b46e90, may_block=1) at gmain.c:2654
#33 0x02384126 in QEventDispatcherGlib::processEvents (this=0x8b18c18, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#34 0x01277796 in QGuiEventDispatcherGlib::processEvents (this=0x8b18c18, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#35 0x0235a4ea in QEventLoop::processEvents (this=0xbfc63194, flags=...) at kernel/qeventloop.cpp:149
#36 0x0235a82a in QEventLoop::exec (this=0xbfc63194, flags=...) at kernel/qeventloop.cpp:201
#37 0x0235e4e7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#38 0x011c8c88 in QApplication::exec () at kernel/qapplication.cpp:3585
#39 0x080a5783 in main (argc=) at /usr/src/debug/konversation-1.3.1/src/main.cpp:101

Reported using DrKonqi
Comment 1 Eike Hein 2010-08-18 16:22:25 UTC
Do you know whether the server tab you closed was for a config-backed connection (i.e. one to a network/server found in your Server List dialog) or to a host not in your config?
Comment 2 Jonas Thiem 2010-08-18 16:24:44 UTC
I just did my usual Konversation startup sequence:
 - Open
 - Ctrl+A in the server list
 - Clicking "Connect"

And then decided I should probably rather not connect to some of the servers and attempted to close the first tab. So it was definitely part of the server list
Comment 3 Myriam Schweingruber 2013-04-14 00:54:07 UTC
Is this still reproducible with Konversation 1.4 or 1.5 RC1? Then we would need
a new backtrace.
Comment 4 Andrew Crouthamel 2018-09-24 01:57:33 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:31:27 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!