Bug 248153 - kopete crashes after exiting while connecting
Summary: kopete crashes after exiting while connecting
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 1.0.0
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-08-17 15:59 UTC by Oleksandr Natalenko
Modified: 2018-09-24 05:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleksandr Natalenko 2010-08-17 15:59:45 UTC
Application: kopete (1.0.0)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.35-pf3 i686
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
I've run some downloads, that grabbed almost all bandwidth of internet channel. Then I decided to connect to jabber server. Kopete had been trying to do this for approximately one minute, then I decided to exit Kopete and disable downloading. After pressing «Quit» Kopete crashed.

 -- Backtrace:
Application: Kopete (kopete), signal: Aborted
[Current thread is 1 (Thread 0xb4970710 (LWP 25935))]

Thread 2 (Thread 0xb04b5b70 (LWP 25957)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb5e8a413 in ?? () from /lib/i686/cmov/libc.so.6
#2  0xb5e22427 in ?? () from /lib/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb4970710 (LWP 25935)):
[KCrash Handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb5ddb751 in raise () from /lib/i686/cmov/libc.so.6
#8  0xb5ddeb82 in abort () from /lib/i686/cmov/libc.so.6
#9  0xb5e1222d in ?? () from /lib/i686/cmov/libc.so.6
#10 0xb5e1c321 in ?? () from /lib/i686/cmov/libc.so.6
#11 0xb5e1f9a0 in ?? () from /lib/i686/cmov/libc.so.6
#12 0xb5e20d2c in malloc () from /lib/i686/cmov/libc.so.6
#13 0xb5fb5ba7 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
#14 0xb5fb5cdd in operator new[](unsigned int) () from /usr/lib/libstdc++.so.6
#15 0xb6b98b39 in QHashData::rehash (this=0xa62be20, hint=1) at tools/qhash.cpp:368
#16 0xb5d30123 in QHashData::willGrow (this=0xa5e01fc, akey=..., avalue=@0xbfed6e54) at ../../include/QtCore/../../src/corelib/tools/qhash.h:163
#17 QHash<QString, QDomNodePrivate*>::insertMulti (this=0xa5e01fc, akey=..., avalue=@0xbfed6e54) at ../../include/QtCore/../../src/corelib/tools/qhash.h:769
#18 0xb5d222ab in QDomNamedNodeMapPrivate::setNamedItem (this=0xa5e01f8, arg=0xa5b36f0) at dom/qdom.cpp:3125
#19 0xb12beda9 in JabberCapabilitiesManager::CapabilitiesInformation::toXml (this=0xa1067fc, doc=0xbfed6fa0) at ../../../../kopete/protocols/jabber/jabbercapabilitiesmanager.cpp:262
#20 0xb12bf1c7 in JabberCapabilitiesManager::saveInformation (this=0xa5aff90) at ../../../../kopete/protocols/jabber/jabbercapabilitiesmanager.cpp:631
#21 0xb12c07ed in ~JabberCapabilitiesManager (this=0xa5aff90, __in_chrg=<value optimized out>) at ../../../../kopete/protocols/jabber/jabbercapabilitiesmanager.cpp:332
#22 0xb127662e in ~JabberProtocol (this=0xa654cf8, __in_chrg=<value optimized out>) at ../../../../kopete/protocols/jabber/jabberprotocol.cpp:140
#23 0xb6c86795 in qDeleteInEventHandler (o=0x0) at kernel/qobject.cpp:4001
#24 0xb6c87e58 in QObject::event (this=0xa654cf8, e=0x6) at kernel/qobject.cpp:1231
#25 0xb61465cc in QApplicationPrivate::notify_helper (this=0x9dbc100, receiver=0xa654cf8, e=0xa47c530) at kernel/qapplication.cpp:4302
#26 0xb614d15e in QApplication::notify (this=0xbfed7884, receiver=0xa654cf8, e=0xa47c530) at kernel/qapplication.cpp:3706
#27 0xb71c6c5a in KApplication::notify (this=0xbfed7884, receiver=0xa654cf8, event=0xa47c530) at ../../kdeui/kernel/kapplication.cpp:302
#28 0xb6c7752b in QCoreApplication::notifyInternal (this=0xbfed7884, receiver=0xa654cf8, event=0xa47c530) at kernel/qcoreapplication.cpp:726
#29 0xb6c7af8c in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9d8db60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#30 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9d8db60) at kernel/qcoreapplication.cpp:1367
#31 0xb6c7b10d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1260
#32 0xb6ca359f in QCoreApplication::sendPostedEvents (s=0x9dbd910) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#33 postEventSourceDispatch (s=0x9dbd910) at kernel/qeventdispatcher_glib.cpp:276
#34 0xb536d2f5 in g_main_dispatch (context=0x9dbd890) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:1960
#35 IA__g_main_context_dispatch (context=0x9dbd890) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2513
#36 0xb5370fd8 in g_main_context_iterate (context=0x9dbd890, block=<value optimized out>, dispatch=1, self=0x9dbb250) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2591
#37 0xb53711b8 in IA__g_main_context_iteration (context=0x9dbd890, may_block=1) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2654
#38 0xb6ca3095 in QEventDispatcherGlib::processEvents (this=0x9d8d650, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#39 0xb6204f45 in QGuiEventDispatcherGlib::processEvents (this=0x9d8d650, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#40 0xb6c75b49 in QEventLoop::processEvents (this=0xbfed77e4, flags=) at kernel/qeventloop.cpp:149
#41 0xb6c75f9a in QEventLoop::exec (this=0xbfed77e4, flags=...) at kernel/qeventloop.cpp:201
#42 0xb6c7b1cf in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#43 0xb6146667 in QApplication::exec () at kernel/qapplication.cpp:3581
#44 0x08059a2e in main (argc=3, argv=0xbfed7cc4) at ../../../kopete/kopete/main.cpp:105

Reported using DrKonqi
Comment 1 Christoph Feck 2013-09-12 21:36:37 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 2 Andrew Crouthamel 2018-09-24 02:07:50 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 3 Oleksandr Natalenko 2018-09-24 05:04:00 UTC
8 years later I don't remember what was this about, and currently it is not applicable to me.