Bug #188836 “kopete-kde4 crashes when connecting to some Jabber ...” : Bugs : kdenetwork package : Ubuntu

Revision history for this message

Harald Sitter (apachelogger) wrote on 2008-02-04:

#1

Got any example servers to try?

Also try installing kdenetwork-dbg-kde4 and check for useful output when starting kopete from konsole.

Changed in kdenetwork-kde4:
status:	New → Incomplete

Revision history for this message

Sergei A. Beilin (sbeilin) wrote on 2008-02-04:

#2

1) jabber.ru is an example. I can use Psi or older Kopete to connect to, but not the latest Kopete. jabber.org now works fine, but friends complain that Google's XMPP server also gets Kopete down (did not test)

2) The last lines to stderr of crashing Kopete are:

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id: 0x633c58
QImage::scaled: Image is a null image
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id: 0x63caf1
QImage::scaled: Image is a null image
kopete(7646) Kopete::AccountManager::setOnlineStatus: category: 2 , Kopete::OnlineStatusManager::Away: 4
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kopete path = <unknown> pid = 7646
Unable to start Dr. Konqi

That'all. (Yes, I have kdenetwork-dbg-kde4 installed)

Revision history for this message

In KDE Bug Tracking System #157316, Arnaud DELCASSE (delcasse) wrote on 2008-02-07:

#23

Download full text (6.7 KiB)

Version: (using Devel)
Installed from: Compiled sources
Compiler: gcc
OS: Linux

When I want to connect to a Jabber account through system tray's icon, Kopete crashes. It happens only with 1 of my Jabber accounts (the one which I deleted a MSN transport in Kopete accounts list).

I'm using Archlinux's "KDEmod" 4.0.1 version of KDE, with Kopete version 0.50.1

Here is the backtrace :

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5ae16d0 (LWP 12561)]
[New Thread 0xb2adcb90 (LWP 12573)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging sym...

Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc 
OS:                Linux

When I want to connect to a Jabber account through system tray's icon, Kopete crashes. It happens only with 1 of my Jabber accounts (the one which I deleted a MSN transport in Kopete accounts list).

I'm using Archlinux's "KDEmod" 4.0.1 version of KDE, with Kopete version 0.50.1

Here is the backtrace :

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5ae16d0 (LWP 12561)]
[New Thread 0xb2adcb90 (LWP 12573)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb6d012e7 in Kopete::Contact::metaContact ()
   from /opt/kdemod/lib/libkopete.so.4
#7  0xb3d1d893 in ChatMessagePart::writeTemplate ()
   from /opt/kdemod/lib/libkopetechatwindow_shared.so.1
#8  0xb3d20e9f in ChatMessagePart::changeStyle ()
   from /opt/kdemod/lib/libkopetechatwindow_shared.so.1
#9  0xb3d211b9 in ChatMessagePart::qt_metacall ()
   from /opt/kdemod/lib/libkopetechatwindow_shared.so.1
#10 0xb7ee5616 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7ee5be2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb7eec0e7 in ?? () from /usr/lib/libQtCore.so.4
#13 0xb7eec12c in ?? () from /usr/lib/libQtCore.so.4
#14 0xb7ee2268 in QObject::event () from /usr/lib/libQtCore.so.4
#15 0xb6ef8b0d in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#16 0xb6efb2c9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb7993d7d in KApplication::notify () from /opt/kdemod/lib/libkdeui.so.5
#18 0xb7ed280b in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#19 0xb7efa3a1 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb7ef71f0 in ?? () from /usr/lib/libQtCore.so.4
#21 0xb5fb9346 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb5fbc6d2 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#23 0xb5fbcc8e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb7ef7762 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#25 0xb6f7c475 in ?? () from /usr/lib/libQtGui.so.4
#26 0xb7ed1bf2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#27 0xb7ed1cfa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#28 0xb7ed41fd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#29 0xb6ef8087 in QApplication::exec () from /usr/lib/libQtGui.so.4
#30 0x0808783a in _start ()
#0  0xb7fa8410 in __kernel_vsyscall ()

Revision history for this message

In KDE Bug Tracking System #157316, Arnaud DELCASSE (delcasse) wrote on 2008-02-07:

#24

In fact, it crashes every time I try to connect to this account, not only when I'm using system tray

Revision history for this message

Gary (pento) wrote on 2008-04-03:

#3

It dies for me when connecting to the Google Talk servers. I get the following error to stderr, but only if the contact list is open:

KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kopete path = <unknown> pid = 14485
Unable to start Dr. Konqi

If the contact list is closed, I just get:

Unable to start Dr. Konqi

I am using kdenetwork-dbg-kde4.

Revision history for this message

In KDE Bug Tracking System #157316, protoman (protomank) wrote on 2008-04-04:

#25

Me too. I have a MSN and ICQ transport in my gtalk accound and kopete in kde4 simply crashes every time.

Revision history for this message

Terence Simpson (tsimpson) wrote on 2008-04-14:

#4

Are you still experiencing this problem with current KDE4 packages?

Revision history for this message

Gary (pento) wrote on 2008-04-14:

#5

Unfortunately I can't test. I downgraded back to Gutsy/KDE3, Hardy/KDE4 was missing a bunch of stuff that I needed.

Revision history for this message

Stephan Rügamer (sruegamer) wrote on 2008-04-16:

#6

Hi,

I confirm this bug. You can try to use my jabber server (jabberme.net/linux-server.org/sourcecode.de) ...
If you need assistance, please catch me on irc :)

Regards,

\sh

Changed in kdenetwork-kde4:
importance:	Undecided → Critical
status:	Incomplete → Confirmed

Revision history for this message

Dennis Nienhüser (earthwings) wrote on 2008-05-01:

#7

I just tried with jabberme.net and it connected fine, Kopete 0.50.1, KDE 4.0.3. Are you still experiencing the problem?

Revision history for this message

Stephan Rügamer (sruegamer) wrote on 2008-05-02:

#8

Now it's getting even worse...

X + computer freezes completly after logging in.

Ok, I tried it with an empty account, this works as expected.
But having a really full account with many jabber buddies+icq transport buddies it's somehow not working.

Revision history for this message

Harald Sitter (apachelogger) wrote on 2008-05-10:

#9

Someone please search/create a report on http://bugs.kde.org

Thank you.

Revision history for this message

In KDE Bug Tracking System #157316, brot (schnitzelkuchen) wrote on 2008-07-20:

#26

Download full text (4.5 KiB)

I can confirm this bug with kopete svn trunk r835161, allthough it only crashes once when adding the jabber account with the transports, after that crash everything works like it should (except if you dare to remove that account again ;) )

kopete(17568)/kopete (jabber) JabberTransport::JabberTransport: "<email address hidden>/icq.foxybanana.com" transport created: myself: JabberContact(0x1c0b610)
ASSERT: "identityItemHash.contains(idnt)" in file /var/tmp/paludis/kde-base-kopete-scm/work/kopete/kopete/kopete/config/accounts/kopeteaccountconfig.cpp, line 181
kopete(17568) ChatWindowStyleManager::~ChatWindowStyleManager:
kopete(17568) ChatWindowStyle::~ChatWindowStyle:
kopete(17568)/libkopete Kopete::PluginManagerPrivate::~PluginManagerPrivate: Destructing plugin manager without going through the shutdown process! Backtrace is:
"[
0: /usr/kde/svn/lib64/libkdecore.so.5(_Z14kRealBacktracei+0x38) [0x7fa28382b908]
1: /usr/kde/svn/lib64/libkopete.so.4 [0x7fa282385ba9]
2: /usr/kde/svn/lib64/libkopete.so.4 [0x7fa2823872e2]
3: /usr/kde/svn/lib64/libkopete.so.4 [0x7fa2823834f2]
4: /lib64/libc.so.6(exit+0x9d) [0x7fa27fd3bddd]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x82) [0x7fa283c04412]
6: /usr/lib64/qt4/libQtCore.so.4(_Z6qFatalPKcz+0xd7) [0x7fa283c04557]
7: /usr/kde/svn/lib64/kde4/kcm_kopete_accountconfig.so [0x7fa2703f3aa8]
8: /usr/kde/svn/lib64/kde4/kcm_kopete_accountconfig.so [0x7fa2703f3707]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x23c) [0x7fa283d3be6c]
10: /usr/kde/svn/lib64/libkopete.so.4(_ZN6Kopete14AccountManager17accountRegisteredEPNS_7AccountE+0x2f) [0x7fa28235223f]
11: /usr/kde/svn/lib64/libkopete.so.4(_ZN6Kopete14AccountManager15registerAccountEPNS_7AccountE+0x1be) [0x7fa28235305e]
12: /usr/kde/svn/lib64/kde4/kopete_jabber.so [0x7fa27273716c]
13: /usr/kde/svn/lib64/kde4/kopete_jabber.so [0x7fa27273b422]
14: /usr/lib64/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x23c) [0x7fa283d3be6c]
15: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP4Task4doneEv+0x3a) [0x7fa2721606fa]
16: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP13DiscoInfoTask4takeERK11QDomElement+0x540) [0x7fa27215f040]
17: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP4Task4takeERK11QDomElement+0x62) [0x7fa272160942]
18: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP6Client10distributeERK11QDomElement+0x114) [0x7fa27212f1f4]
19: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP6Client15streamReadyReadEv+0x150) [0x7fa27212fc20]
20: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP6Client11qt_metacallEN11QMetaObject4CallEiPPv+0x225) [0x7fa2720ef4a5]
21: /usr/lib64/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x23c) [0x7fa283d3be6c]
22: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP12ClientStream11qt_metacallEN11QMetaObject4CallEiPPv+0x242) [0x7fa2720ef052]
23: /usr/lib64/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x23c) [0x7fa283d3be6c]
24: /usr/lib64/qt4/libQtCore.so.4 [0x7fa283d44fea]
25: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0xb3) [0x7fa283d35673]
26: /usr/lib64/qt4/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xbd) [0x7fa280...

I can confirm this bug with kopete svn trunk r835161, allthough it only crashes once when adding the jabber account with the transports, after that crash everything works like it should (except if you dare to remove that account again ;) )

kopete(17568)/kopete (jabber) JabberTransport::JabberTransport: "brot@foxybanana.com/icq.foxybanana.com"  transport created:  myself:  JabberContact(0x1c0b610)
ASSERT: "identityItemHash.contains(idnt)" in file /var/tmp/paludis/kde-base-kopete-scm/work/kopete/kopete/kopete/config/accounts/kopeteaccountconfig.cpp, line 181
kopete(17568) ChatWindowStyleManager::~ChatWindowStyleManager:
kopete(17568) ChatWindowStyle::~ChatWindowStyle:
kopete(17568)/libkopete Kopete::PluginManagerPrivate::~PluginManagerPrivate: Destructing plugin manager without going through the shutdown process! Backtrace is:
"[
0: /usr/kde/svn/lib64/libkdecore.so.5(_Z14kRealBacktracei+0x38) [0x7fa28382b908]
1: /usr/kde/svn/lib64/libkopete.so.4 [0x7fa282385ba9]
2: /usr/kde/svn/lib64/libkopete.so.4 [0x7fa2823872e2]
3: /usr/kde/svn/lib64/libkopete.so.4 [0x7fa2823834f2]
4: /lib64/libc.so.6(exit+0x9d) [0x7fa27fd3bddd]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x82) [0x7fa283c04412]
6: /usr/lib64/qt4/libQtCore.so.4(_Z6qFatalPKcz+0xd7) [0x7fa283c04557]
7: /usr/kde/svn/lib64/kde4/kcm_kopete_accountconfig.so [0x7fa2703f3aa8]
8: /usr/kde/svn/lib64/kde4/kcm_kopete_accountconfig.so [0x7fa2703f3707]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x23c) [0x7fa283d3be6c]
10: /usr/kde/svn/lib64/libkopete.so.4(_ZN6Kopete14AccountManager17accountRegisteredEPNS_7AccountE+0x2f) [0x7fa28235223f]
11: /usr/kde/svn/lib64/libkopete.so.4(_ZN6Kopete14AccountManager15registerAccountEPNS_7AccountE+0x1be) [0x7fa28235305e]
12: /usr/kde/svn/lib64/kde4/kopete_jabber.so [0x7fa27273716c]
13: /usr/kde/svn/lib64/kde4/kopete_jabber.so [0x7fa27273b422]
14: /usr/lib64/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x23c) [0x7fa283d3be6c]
15: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP4Task4doneEv+0x3a) [0x7fa2721606fa]
16: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP13DiscoInfoTask4takeERK11QDomElement+0x540) [0x7fa27215f040]
17: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP4Task4takeERK11QDomElement+0x62) [0x7fa272160942]
18: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP6Client10distributeERK11QDomElement+0x114) [0x7fa27212f1f4]
19: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP6Client15streamReadyReadEv+0x150) [0x7fa27212fc20]
20: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP6Client11qt_metacallEN11QMetaObject4CallEiPPv+0x225) [0x7fa2720ef4a5]
21: /usr/lib64/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x23c) [0x7fa283d3be6c]
22: /usr/kde/svn/lib64/libiris_kopete.so.1(_ZN4XMPP12ClientStream11qt_metacallEN11QMetaObject4CallEiPPv+0x242) [0x7fa2720ef052]
23: /usr/lib64/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x23c) [0x7fa283d3be6c]
24: /usr/lib64/qt4/libQtCore.so.4 [0x7fa283d44fea]
25: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0xb3) [0x7fa283d35673]
26: /usr/lib64/qt4/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xbd) [0x7fa2804f9ffd]
27: /usr/lib64/qt4/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x9a) [0x7fa2804fb53a]
28: /usr/kde/svn/lib64/libkdeui.so.5(_ZN12KApplication6notifyEP7QObjectP6QEvent+0x3b) [0x7fa2830f5eab]
29: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0xd0) [0x7fa283d23bd0]
30: /usr/lib64/qt4/libQtCore.so.4 [0x7fa283d54855]
31: /usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x128) [0x7fa283d564d8]
32: /usr/lib64/qt4/libQtGui.so.4 [0x7fa28059bd4a]
33: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x32) [0x7fa283d22812]
34: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x19d) [0x7fa283d22cad]
35: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xbf) [0x7fa283d283ef]
36: kopete [0x444c61]
37: /lib64/libc.so.6(__libc_start_main+0xe6) [0x7fa27fd25486]
38: kopete(_ZN10Q3ListView18drawContentsOffsetEP8QPainteriiiiii+0x79) [0x423e99]
]
"
kopete(17568)/libkopete Kopete::PluginManagerPrivate::~PluginManagerPrivate: Deleting stale plugin ' "" '
Fatal Error: Accessed global static 'MessageHandlerFactory::FactoryList *g_list()' after destruction. Defined at /var/tmp/paludis/kde-base-kopete-scm/work/kopete/kopete/libkopete/kopetemessagehandler.cpp:82

Revision history for this message

In KDE Bug Tracking System #157316, Mlroper (mlroper) wrote on 2008-07-28:

#27

I am experiencing this issue, though without any MSN account complications.

Kopete crashes shortly after connecting to a Jabber server (in this case, the Jabber server is powered by Openfire 3.5.1).

After connecting to the Jabber account, the contacts pane is momentarily populated with Jabber contacts before the application immediately crashes.

Here is the backtrace (redundant lines replaced with "..."):

(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5a9f720 (LWP 7535)]
[New Thread 0xb2f27b90 (LWP 7539)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#6 0xb652c9bc in memcpy () from /lib/tls/i686/cmov/libc.so.6
#7 0xb7ca21da in ?? () from /usr/lib/kde4/lib/libkdecore.so.5
#8 0xb7c8e269 in KNetwork::KBufferedSocket::slotWriteActivity ()
   from /usr/lib/kde4/lib/libkdecore.so.5
#9 0xb7c8e04b in KNetwork::KBufferedSocket::qt_metacall ()
   from /usr/lib/kde4/lib/libkdecore.so.5
#10 0xb7e884f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7e88bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb7ec5ca3 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#13 0xb7e8eb8f in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#14 0xb6e26c0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#15 0xb6e2b7a9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#16 0xb79acc93 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#17 0xb7e736a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#18 0xb7e9ee23 in ?? () from /usr/lib/libQtCore.so.4
#19 0xb641bbf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb641ee5e in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb641f3ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb7e9ef98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#23 0xb6eba1b5 in ?? () from /usr/lib/libQtGui.so.4
#24 0xb7e7292d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb7e72abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#26 0xb7e74d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#27 0xb6e26567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#28 0x0808732b in ?? ()
#29 0xb64cf450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#30 0x080637a1 in _start ()
#0 0xb7f7e410 in __kernel_vsyscall ()

I am experiencing this issue, though without any MSN account complications.

Kopete crashes shortly after connecting to a Jabber server (in this case, the Jabber server is powered by Openfire 3.5.1).

After connecting to the Jabber account, the contacts pane is momentarily populated with Jabber contacts before the application immediately crashes.

Here is the backtrace (redundant lines replaced with "..."):

(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5a9f720 (LWP 7535)]
[New Thread 0xb2f27b90 (LWP 7539)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#6  0xb652c9bc in memcpy () from /lib/tls/i686/cmov/libc.so.6
#7  0xb7ca21da in ?? () from /usr/lib/kde4/lib/libkdecore.so.5
#8  0xb7c8e269 in KNetwork::KBufferedSocket::slotWriteActivity ()
   from /usr/lib/kde4/lib/libkdecore.so.5
#9  0xb7c8e04b in KNetwork::KBufferedSocket::qt_metacall ()
   from /usr/lib/kde4/lib/libkdecore.so.5
#10 0xb7e884f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7e88bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb7ec5ca3 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#13 0xb7e8eb8f in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#14 0xb6e26c0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#15 0xb6e2b7a9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#16 0xb79acc93 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#17 0xb7e736a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#18 0xb7e9ee23 in ?? () from /usr/lib/libQtCore.so.4
#19 0xb641bbf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb641ee5e in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb641f3ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb7e9ef98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#23 0xb6eba1b5 in ?? () from /usr/lib/libQtGui.so.4
#24 0xb7e7292d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb7e72abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#26 0xb7e74d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#27 0xb6e26567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#28 0x0808732b in ?? ()
#29 0xb64cf450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#30 0x080637a1 in _start ()
#0  0xb7f7e410 in __kernel_vsyscall ()

Revision history for this message

mehturt (mehturt) wrote on 2008-07-30:

#10

backtrace Edit (5.7 KiB, text/plain)

I have similar problem with our company jabber server..
The console error is:
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kopete path = <unknown> pid = 25278
kdeinit4: Got EXEC_NEW '/usr/lib/kde4/lib/kde4/libexec/drkonqi' from socket.
kdeinit4: preparing to launch /usr/lib/kde4/lib/kde4/libexec/drkonqi
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1608159)

The backtrace is attached.

Revision history for this message

mehturt (mehturt) wrote on 2008-07-30:

#11

I added my backtrace to this bug, http://bugs.kde.org/show_bug.cgi?id=157316 because it looks similar/related.

Revision history for this message

In KDE Bug Tracking System #157316, mehturt (mehturt) wrote on 2008-07-30:

#28

I'm seeing similar problem when connecting to OpenFire 3.5.2 jabber server.
I'm using kopete 4:4.1.0-0ubuntu1~hardy1~ppa1 from http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu on amd64.
I'll attach the backtrace.
I can provide more info if necessary.

Revision history for this message

In KDE Bug Tracking System #157316, mehturt (mehturt) wrote on 2008-07-30:

#29

Created attachment 26489
backtrace

Revision history for this message

In KDE Bug Tracking System #157316, James Lamb (admin-oranged) wrote on 2008-07-30:

#30

Created attachment 26493
kopete kcrash debug output

Attached is my backtrace as I have been having the same issues when connecting
to jabber on KDE 4.0 and 4.1

Revision history for this message

scor (omgbebebe) wrote on 2008-08-08:

#12

Hi!

I confirm this bug to. I use kubuntu hardy and kde 4.1. When i reinstall qca-tls package, crashes gone and now kopete work well. I don`t know may it help or not, btw i happy now:))

Jonathan Thomas (echidnaman) on 2008-08-20

Changed in kdenetwork:
status:	New → Unknown

Bug Watch Updater (bug-watch-updater) on 2008-08-20

Changed in kdenetwork:
status:	Unknown → New

Revision history for this message

Kevin Christmas (kachristmas) wrote on 2008-09-05:

#13

Download full text (3.6 KiB)

Crashes when connecting to an Openfire (open source) jabber server over SSL.

Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe07138b780 (LWP 7092)]
[New Thread 0x43379950 (LWP 7097)]
[New Thread 0x4102e950 (LWP 7093)]
[KCrash handler]
#5 0x00007fe06d050f82 in memcpy () from /lib/libc.so.6
#6 0x00007fe06fb0eb51 in KNetwork::Internal::KSocketBuffer::sendTo (
    this=0x1103750, dev=0x117be60, len=-1)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3socketbuffer.cpp:256
#7 0x00007fe06fafe408 in KNetwork::KBufferedSocket::slotWriteActivity (
    this=0x1136d00)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3bufferedsocket.cpp:349
#8 0x00007fe06fafe292 in KNetwork::KBufferedSocket::qt_metacall (
    this=0x1136d00, _c=QMetaObject::InvokeMetaMethod, _id=1,
    _a=<value optimized out>)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-x86_64-linux-gnu/kdecore/k3bufferedsocket.moc:68
#9 0x00007fe06f46a8b6 in QMetaObject::activate (sender=0xab5d50,
    from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1783)
    at kernel/qobject.cpp:3016
#10 0x00007fe06f4a3fae in QSocketNotifier::activated (this=0x1296dba, _t1=29)
    at .moc/release-shared/moc_qsocketnotifier.cpp:81
#11 0x00007fe06f470b5f in QSocketNotifier::event (this=0xab5d50,
    e=0x7fff793d0ad0) at kernel/qsocketnotifier.cpp:326
#12 0x00007fe06dd34acf in QApplicationPrivate::notify_helper (this=0x6ae8c0,
    receiver=0xab5d50, e=0x7fff793d0ad0) at kernel/qapplication.cpp:3800
#13 0x00007fe06dd36c85 in QApplication::notify (this=0x7fff793d0db0,
    receiver=0xab5d50, e=0x7fff793d0ad0) at kernel/qapplication.cpp:3765
#14 0x00007fe06ffecea1 in KApplication::notify (this=0x7fff793d0db0,
    receiver=0xab5d50, event=0x7fff793d0ad0)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311
#15 0x00007fe06f4566b9 in QCoreApplication::notifyInternal (
    this=0x7fff793d0db0, receiver=0xab5d50, event=0x7fff793d0ad0)
    at kernel/qcoreapplication.cpp:591
#16 0x00007fe06f47f85a in socketNotifierSourceDispatch (source=0x6b1bb0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#17 0x00007fe06a0cb02a in IA__g_main_context_dispatch (context=0x6b10e0)
    at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2073
#18 0x00007fe06a0cdfe5 in g_main_context_iterate (context=0x6b10e0, block=1,
    dispatch=1, self=<value optimized out>)
    at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2706
#19 0x00007fe06a0ce507 in IA__g_main_context_iteration (context=0x6b10e0,
    may_block=1) at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2769
#20 0x00007fe06f47f9df in QEventDispatcherGlib::processEvents (this=0x6966f0,
    flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:325
#21 0x00007fe06ddbe20f in QGuiEventDispatcherGlib::processEvents (
    this=0x1296dba, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fe06f455b35 in QEventLoop::processE...

Crashes when connecting to an Openfire (open source) jabber server over SSL.

Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe07138b780 (LWP 7092)]
[New Thread 0x43379950 (LWP 7097)]
[New Thread 0x4102e950 (LWP 7093)]
[KCrash handler]
#5  0x00007fe06d050f82 in memcpy () from /lib/libc.so.6
#6  0x00007fe06fb0eb51 in KNetwork::Internal::KSocketBuffer::sendTo (
    this=0x1103750, dev=0x117be60, len=-1)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3socketbuffer.cpp:256
#7  0x00007fe06fafe408 in KNetwork::KBufferedSocket::slotWriteActivity (
    this=0x1136d00)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3bufferedsocket.cpp:349
#8  0x00007fe06fafe292 in KNetwork::KBufferedSocket::qt_metacall (
    this=0x1136d00, _c=QMetaObject::InvokeMetaMethod, _id=1, 
    _a=<value optimized out>)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-x86_64-linux-gnu/kdecore/k3bufferedsocket.moc:68
#9  0x00007fe06f46a8b6 in QMetaObject::activate (sender=0xab5d50, 
    from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1783)
    at kernel/qobject.cpp:3016
#10 0x00007fe06f4a3fae in QSocketNotifier::activated (this=0x1296dba, _t1=29)
    at .moc/release-shared/moc_qsocketnotifier.cpp:81
#11 0x00007fe06f470b5f in QSocketNotifier::event (this=0xab5d50, 
    e=0x7fff793d0ad0) at kernel/qsocketnotifier.cpp:326
#12 0x00007fe06dd34acf in QApplicationPrivate::notify_helper (this=0x6ae8c0, 
    receiver=0xab5d50, e=0x7fff793d0ad0) at kernel/qapplication.cpp:3800
#13 0x00007fe06dd36c85 in QApplication::notify (this=0x7fff793d0db0, 
    receiver=0xab5d50, e=0x7fff793d0ad0) at kernel/qapplication.cpp:3765
#14 0x00007fe06ffecea1 in KApplication::notify (this=0x7fff793d0db0, 
    receiver=0xab5d50, event=0x7fff793d0ad0)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311
#15 0x00007fe06f4566b9 in QCoreApplication::notifyInternal (
    this=0x7fff793d0db0, receiver=0xab5d50, event=0x7fff793d0ad0)
    at kernel/qcoreapplication.cpp:591
#16 0x00007fe06f47f85a in socketNotifierSourceDispatch (source=0x6b1bb0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#17 0x00007fe06a0cb02a in IA__g_main_context_dispatch (context=0x6b10e0)
    at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2073
#18 0x00007fe06a0cdfe5 in g_main_context_iterate (context=0x6b10e0, block=1, 
    dispatch=1, self=<value optimized out>)
    at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2706
#19 0x00007fe06a0ce507 in IA__g_main_context_iteration (context=0x6b10e0, 
    may_block=1) at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2769
#20 0x00007fe06f47f9df in QEventDispatcherGlib::processEvents (this=0x6966f0, 
    flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:325
#21 0x00007fe06ddbe20f in QGuiEventDispatcherGlib::processEvents (
    this=0x1296dba, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fe06f455b35 in QEventLoop::processEvents (
    this=<value optimized out>, flags=@0x7fff793d0ce0)
    at kernel/qeventloop.cpp:149
#23 0x00007fe06f455c8b in QEventLoop::exec (this=0x7fff793d0d20, 
    flags=@0x7fff793d0d30) at kernel/qeventloop.cpp:200
#24 0x00007fe06f457cd9 in QCoreApplication::exec ()
    at kernel/qcoreapplication.cpp:849
#25 0x00000000004441f1 in ?? ()
#26 0x00007fe06cff21c4 in __libc_start_main () from /lib/libc.so.6
#27 0x0000000000423be9 in _start ()
#0  0x00007fe06d071b81 in nanosleep () from /lib/libc.so.6

Revision history for this message

In KDE Bug Tracking System #157316, Kevin Christmas (kachristmas) wrote on 2008-09-05:

#31

Download full text (3.6 KiB)

I can confirm that this is effecting me when I try to connect to an openfire jabber server

Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe07138b780 (LWP 7092)]
[New Thread 0x43379950 (LWP 7097)]
[New Thread 0x4102e950 (LWP 7093)]
[KCrash handler]
#5 0x00007fe06d050f82 in memcpy () from /lib/libc.so.6
#6 0x00007fe06fb0eb51 in KNetwork::Internal::KSocketBuffer::sendTo (
    this=0x1103750, dev=0x117be60, len=-1)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3socketbuffer.cpp:256
#7 0x00007fe06fafe408 in KNetwork::KBufferedSocket::slotWriteActivity (
    this=0x1136d00)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3bufferedsocket.cpp:349
#8 0x00007fe06fafe292 in KNetwork::KBufferedSocket::qt_metacall (
    this=0x1136d00, _c=QMetaObject::InvokeMetaMethod, _id=1,
    _a=<value optimized out>)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-x86_64-linux-gnu/kdecore/k3bufferedsocket.moc:68
#9 0x00007fe06f46a8b6 in QMetaObject::activate (sender=0xab5d50,
    from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1783)
    at kernel/qobject.cpp:3016
#10 0x00007fe06f4a3fae in QSocketNotifier::activated (this=0x1296dba, _t1=29)
    at .moc/release-shared/moc_qsocketnotifier.cpp:81
#11 0x00007fe06f470b5f in QSocketNotifier::event (this=0xab5d50,
    e=0x7fff793d0ad0) at kernel/qsocketnotifier.cpp:326
#12 0x00007fe06dd34acf in QApplicationPrivate::notify_helper (this=0x6ae8c0,
    receiver=0xab5d50, e=0x7fff793d0ad0) at kernel/qapplication.cpp:3800
#13 0x00007fe06dd36c85 in QApplication::notify (this=0x7fff793d0db0,
    receiver=0xab5d50, e=0x7fff793d0ad0) at kernel/qapplication.cpp:3765
#14 0x00007fe06ffecea1 in KApplication::notify (this=0x7fff793d0db0,
    receiver=0xab5d50, event=0x7fff793d0ad0)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311
#15 0x00007fe06f4566b9 in QCoreApplication::notifyInternal (
    this=0x7fff793d0db0, receiver=0xab5d50, event=0x7fff793d0ad0)
    at kernel/qcoreapplication.cpp:591
#16 0x00007fe06f47f85a in socketNotifierSourceDispatch (source=0x6b1bb0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#17 0x00007fe06a0cb02a in IA__g_main_context_dispatch (context=0x6b10e0)
    at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2073
#18 0x00007fe06a0cdfe5 in g_main_context_iterate (context=0x6b10e0, block=1,
    dispatch=1, self=<value optimized out>)
    at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2706
#19 0x00007fe06a0ce507 in IA__g_main_context_iteration (context=0x6b10e0,
    may_block=1) at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2769
#20 0x00007fe06f47f9df in QEventDispatcherGlib::processEvents (this=0x6966f0,
    flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:325
#21 0x00007fe06ddbe20f in QGuiEventDispatcherGlib::processEvents (
    this=0x1296dba, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fe06f455b35 in QEvent...

I can confirm that this is effecting me when I try to connect to an openfire jabber server

Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe07138b780 (LWP 7092)]
[New Thread 0x43379950 (LWP 7097)]
[New Thread 0x4102e950 (LWP 7093)]
[KCrash handler]
#5  0x00007fe06d050f82 in memcpy () from /lib/libc.so.6
#6  0x00007fe06fb0eb51 in KNetwork::Internal::KSocketBuffer::sendTo (
    this=0x1103750, dev=0x117be60, len=-1)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3socketbuffer.cpp:256
#7  0x00007fe06fafe408 in KNetwork::KBufferedSocket::slotWriteActivity (
    this=0x1136d00)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3bufferedsocket.cpp:349
#8  0x00007fe06fafe292 in KNetwork::KBufferedSocket::qt_metacall (
    this=0x1136d00, _c=QMetaObject::InvokeMetaMethod, _id=1, 
    _a=<value optimized out>)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-x86_64-linux-gnu/kdecore/k3bufferedsocket.moc:68
#9  0x00007fe06f46a8b6 in QMetaObject::activate (sender=0xab5d50, 
    from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1783)
    at kernel/qobject.cpp:3016
#10 0x00007fe06f4a3fae in QSocketNotifier::activated (this=0x1296dba, _t1=29)
    at .moc/release-shared/moc_qsocketnotifier.cpp:81
#11 0x00007fe06f470b5f in QSocketNotifier::event (this=0xab5d50, 
    e=0x7fff793d0ad0) at kernel/qsocketnotifier.cpp:326
#12 0x00007fe06dd34acf in QApplicationPrivate::notify_helper (this=0x6ae8c0, 
    receiver=0xab5d50, e=0x7fff793d0ad0) at kernel/qapplication.cpp:3800
#13 0x00007fe06dd36c85 in QApplication::notify (this=0x7fff793d0db0, 
    receiver=0xab5d50, e=0x7fff793d0ad0) at kernel/qapplication.cpp:3765
#14 0x00007fe06ffecea1 in KApplication::notify (this=0x7fff793d0db0, 
    receiver=0xab5d50, event=0x7fff793d0ad0)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311
#15 0x00007fe06f4566b9 in QCoreApplication::notifyInternal (
    this=0x7fff793d0db0, receiver=0xab5d50, event=0x7fff793d0ad0)
    at kernel/qcoreapplication.cpp:591
#16 0x00007fe06f47f85a in socketNotifierSourceDispatch (source=0x6b1bb0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#17 0x00007fe06a0cb02a in IA__g_main_context_dispatch (context=0x6b10e0)
    at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2073
#18 0x00007fe06a0cdfe5 in g_main_context_iterate (context=0x6b10e0, block=1, 
    dispatch=1, self=<value optimized out>)
    at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2706
#19 0x00007fe06a0ce507 in IA__g_main_context_iteration (context=0x6b10e0, 
    may_block=1) at /home/kchristmas/src/glib2.0-2.17.7/glib/gmain.c:2769
#20 0x00007fe06f47f9df in QEventDispatcherGlib::processEvents (this=0x6966f0, 
    flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:325
#21 0x00007fe06ddbe20f in QGuiEventDispatcherGlib::processEvents (
    this=0x1296dba, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fe06f455b35 in QEventLoop::processEvents (
    this=<value optimized out>, flags=@0x7fff793d0ce0)
    at kernel/qeventloop.cpp:149
#23 0x00007fe06f455c8b in QEventLoop::exec (this=0x7fff793d0d20, 
    flags=@0x7fff793d0d30) at kernel/qeventloop.cpp:200
#24 0x00007fe06f457cd9 in QCoreApplication::exec ()
    at kernel/qcoreapplication.cpp:849
#25 0x00000000004441f1 in ?? ()
#26 0x00007fe06cff21c4 in __libc_start_main () from /lib/libc.so.6
#27 0x0000000000423be9 in _start ()
#0  0x00007fe06d071b81 in nanosleep () from /lib/libc.so.6

Revision history for this message

In KDE Bug Tracking System #157316, Marcel Schaal (marcelschaal) wrote on 2008-09-07:

#32

*** This bug has been confirmed by popular vote. ***

Bug Watch Updater (bug-watch-updater) on 2008-09-07

Changed in kdenetwork:
status:	New → Confirmed

Revision history for this message

In KDE Bug Tracking System #157316, Me-ngeefk4xayt3t4u9watah405veq (me-ngeefk4xayt3t4u9watah405veq) wrote on 2008-09-08:

#33

*** Bug 170374 has been marked as a duplicate of this bug. ***

Jonathan Thomas (echidnaman) on 2008-09-10

Changed in kdenetwork:
importance:	Critical → High

Revision history for this message

In KDE Bug Tracking System #157316, Jonathan Thomas (echidnaman-f) wrote on 2008-10-10:

#34

Bug 170684 is a dupe of this too.

Revision history for this message

In KDE Bug Tracking System #157316, Alan Jones (skyphyr) wrote on 2008-12-29:

#35

Thanks for reporting. If somebody could repro on a recent build with debug symbols and provide a new backtrace that would be very helpful.

Cheers,

Alan.

Revision history for this message

Jonathan Thomas (echidnaman) wrote on 2009-01-07:

#14

Is this still an issue for anybody using KDE 4.2 beta2? Upstream would like to see if this is still an issue in a more recent version of KDE.

If it is, could somebody install kdenetwork-dbg and get a new backtrace? Thanks.

Changed in kdenetwork:
status:	Confirmed → Incomplete

Revision history for this message

Kevin Christmas (kachristmas) wrote on 2009-01-07:

#15

I'm connecting to the finicky jabber server perfectly with the version of kopete in KDE 4.2b2.

However, kopete will crash if I manually disconnect from the finicky jabber server. I thought I had the debug packages installed, but I don't. I will install them now.

Revision history for this message

mehturt (mehturt) wrote on 2009-01-07:

#16

I can confirm the same, connect to jabber works now, sending receiving messages is ok. Manual disconnect causes application to crash, though I don't have core file created.
The console output is:

KCrash: Application 'kopete' crashing...
sock_file=/home/liptak/.kde/socket-liptak-laptop/kdeinit4__0
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
QWidget: Must construct a QApplication before a QPaintDevice

Revision history for this message

Kevin Christmas (kachristmas) wrote on 2009-01-07:

#17

mehturt, I couldn't get a backtrace on the disconnect for some reason. Could you add one to the bug I filed upstream?

https://bugs.kde.org/show_bug.cgi?id=179885

Thanks.

Revision history for this message

mehturt (mehturt) wrote on 2009-01-07:

#18

Ok, I attached to kopete via gdb and changed the status to Offline, this is what I got:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fddea1346f0 (LWP 16546)]
0x0000000000000001 in ?? ()
(gdb) bt
#0 0x0000000000000001 in ?? ()
#1 0x00007fdde50262c5 in QMetaObject::invokeMethod () from /usr/lib/libQtCore.so.4
#2 0x00007fdde62bd424 in QAbstractSocket::disconnectFromHost () from /usr/lib/libQtNetwork.so.4
#3 0x00007fdde62c0a98 in ?? () from /usr/lib/libQtNetwork.so.4
#4 0x00007fdde62b1991 in ?? () from /usr/lib/libQtNetwork.so.4
#5 0x00007fdde42ecc3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#6 0x00007fdde42f49ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#7 0x00007fdde5bf4f0b in KApplication::notify () from /usr/lib/libkdeui.so.5
#8 0x00007fdde501dd61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#9 0x00007fdde50463d9 in ?? () from /usr/lib/libQtCore.so.4
#10 0x00007fdddf98fd3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0x00007fdddf99350d in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x00007fdddf9936cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#13 0x00007fdde504615f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#14 0x00007fdde437ea6f in ?? () from /usr/lib/libQtGui.so.4
#15 0x00007fdde501c682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#16 0x00007fdde501c80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#17 0x00007fdde501ecbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#18 0x0000000000449f8c in main (argc=1, argv=0x7ffff2173328) at /build/buildd/kdenetwork-4.1.85/kopete/kopete/main.cpp:102

Is that sufficient?

Revision history for this message

Kevin Christmas (kachristmas) wrote on 2009-01-07:

#19

Yes, that should be fine. Thank you. I'll copy that to the bug I filed upstream.

Revision history for this message

In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote on 2009-01-08:

#36

I am seeing this bug in Kubuntu 8.10, using Kopete 0.60.3, using KDE 4.1.3. I'm seeing approximately the same traceback as has previously been reported, and only when connecting to my companys Openfire server, with 100+ contacts on it. My connection to jabber.org seems to work without issue.

I will try to download and compile a kopete to give a more complete backtrace. Thank you.

Revision history for this message

In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote on 2009-01-09:

#37

Created attachment 30059
Crash log from kopete crash (9-Jan-2009)

Okay. I rebuilt from trunk today, and get the following crash when I try to connect to the corporate OpenFire 3.5.1 server. As earlier mentioned, there are 120 or more contacts on my contact list (preconfigured for all in the company) and while they seem to be loading into the buddy list window, the app then crashes. Attached is the save from the KDE crash handler.

Revision history for this message

In KDE Bug Tracking System #157316, Kevin Christmas (kachristmas) wrote on 2009-01-09:

#38

My office uses Openfire 3.4.5. Using the Kopete Version 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)), I have NOT experienced any problems connecting to the Openfire Jabber server.

Chris Ross's experience suggests a regression or a difference in XMPP server implementations that a fix missed?

Revision history for this message

In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote on 2009-01-09:

#39

Perhaps. How many contacts do you have in your contact list on that jabber server, however? Other folks in this bug chain have also, like me, mentioned that they have many dozen, or even hundreds, of contacts, so I suspect that may be related.
If you're being notified of many dozens or hundreds of contacts being available as well, then your conclusion is likely the correct one.

Revision history for this message

In KDE Bug Tracking System #157316, Kevin Christmas (kachristmas) wrote on 2009-01-09:

#40

There are 74 out of 122 people online and connected to my company's Jabber server. So yeah, I have more than a few dozen on my contact list.

Jonathan Thomas (echidnaman) on 2009-01-10

Changed in kdenetwork:
status:	Incomplete → Triaged

Revision history for this message

In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote on 2009-01-16:

#41

Has there been any headway on this? I'd hate to have to install all of the additional GNOME crud to get Pidgin working, but may need to do so to be able to chatter with my coworkers.

Alan, have you had a chance to look into this, and is the crash log I provided sufficient?

Thanks.

Revision history for this message

In KDE Bug Tracking System #157316, mehturt (mehturt) wrote on 2009-01-16:

#42

<offtopic>you don't need GNOME to get Pidgin running, just GTK</offtopic>

Revision history for this message

In KDE Bug Tracking System #157316, Kevin Christmas (kachristmas) wrote on 2009-01-16:

#43

I upgraded to the new RC1 yesterday. Using the Kopete KDE 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)), I'm still not experiencing any problems establishing a connection to my company's OpenFire jabber server.

Revision history for this message

In KDE Bug Tracking System #157316, mehturt (mehturt) wrote on 2009-01-16:

#44

I can confirm that. Using Kopete 0.60.82 and KDE 4.1.96 it works for me too.

Revision history for this message

In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote on 2009-01-16:

#45

Interesting. I just tried to run a trunk build from today (Kopete Version 0.70.50, using the installed KDE 4.1.3) and the first time I connected, I saw most of the contact information load, then it crashed. Or at least, it exited (was running --nofork). I tried again, and it seemed to cope. It connected, then disconnected for some reason but remained running. I was able to reconnect, and now it shows all 91/199 contacts for that server.

:-/ I'm not sure about this. I hate inconsistent bugs.

Revision history for this message

In KDE Bug Tracking System #157316, hydralien (hydralien) wrote on 2009-02-02:

#46

Download full text (5.9 KiB)

Issuing the same on Ubuntu 8.10 in Kopete version 4:4.1.3 (from what ubuntu says). I'm using SSL on jabber connection (not sure if that matters) and my contact list also contains >100 records.

Are there any updates/status for this bug?

Here's crash report:

Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb59016c0 (LWP 29189)]
[New Thread 0xb30afb90 (LWP 29190)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols...

Issuing the same on Ubuntu 8.10 in Kopete version 4:4.1.3 (from what ubuntu says). I'm using SSL on jabber connection (not sure if that matters) and my contact list also contains >100 records.

Are there any updates/status for this bug?

Here's crash report:

Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb59016c0 (LWP 29189)]
[New Thread 0xb30afb90 (LWP 29190)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb6449b71 in memcpy () from /lib/tls/i686/cmov/libc.so.6
#7  0xb77c63f0 in ?? () from /usr/lib/libkdecore.so.5
#8  0xb77b0350 in KNetwork::KBufferedSocket::slotWriteActivity ()
   from /usr/lib/libkdecore.so.5
#9  0xb77b0180 in KNetwork::KBufferedSocket::qt_metacall ()
   from /usr/lib/libkdecore.so.5
#10 0xb758ca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb758d7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb75c7633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#13 0xb7592637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#14 0xb6a598ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#15 0xb6a6172e in QApplication::notify () from /usr/lib/libQtGui.so.4
#16 0xb7ab7b2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#17 0xb7577e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#18 0xb75a270a in ?? () from /usr/lib/libQtCore.so.4
#19 0xb5f5a6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb5f5dda3 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb5f5df61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb75a2478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#23 0xb6af3ea5 in ?? () from /usr/lib/libQtGui.so.4
#24 0xb757652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb75766ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#26 0xb7578da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#27 0xb6a59767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#28 0x0808aa6f in _start ()
#0  0xb804a430 in __kernel_vsyscall ()

Jonathan Thomas (echidnaman) on 2009-02-03

Changed in kdenetwork:
importance:	High → Medium

Revision history for this message

capi /. (barraponto) wrote on 2009-05-03:

#20

i'm using jaunty kopete 0.70.2 on kde 4.2.2 and it both connects and disconnects from gtalk servers...
maybe this bug was fixed.

tags:

added: kopete

Revision history for this message

aurelieng (aurelien-grosdidier) wrote on 2009-05-13:

#21

I'm using Jaunty, Kopete 0.70.2 and KDE 4.2.3, and it keeps connecting/disconnecting with a time period of a few seconds to one hour. Very strange behaviour.

Revision history for this message

In KDE Bug Tracking System #157316, Dario Andres (andresbajotierra) wrote on 2009-05-29:

#47

Is this still valid with an updated KDE version ? Thanks

Revision history for this message

In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote on 2009-05-29:

#48

I no longer see this bug in Kubuntu 9.10, which [I believe] is using KDE 4.2.2. Whatever the "norm" in Kubuntu 9.10. "Works for me".

Revision history for this message

In KDE Bug Tracking System #157316, Dario Andres (andresbajotierra) wrote on 2009-05-31:

#49

Thanks, let's wait for the reporter reply.

Bug Watch Updater (bug-watch-updater) on 2009-05-31

Changed in kdenetwork:
status:	Confirmed → Unknown

Revision history for this message

Jonathan Thomas (echidnaman) wrote on 2009-05-31:

#22

This should work in KDE 4.2.2, and since there haven't been any reports of crashes for a long time I'm closing this bug.

Changed in kdenetwork (Ubuntu):
status:	Triaged → Fix Released

Bug Watch Updater (bug-watch-updater) on 2011-02-27

Changed in kdenetwork:
importance:	Unknown → High
status:	Unknown → Incomplete

Revision history for this message

In KDE Bug Tracking System #157316, Andrew-crouthamel (andrew-crouthamel) wrote on 2018-09-19:

#50

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 mark the bug 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!

Revision history for this message

In KDE Bug Tracking System #157316, Andrew-crouthamel (andrew-crouthamel) wrote on 2018-10-21:

#51

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!

Bug Watch Updater (bug-watch-updater) on 2018-11-07

Changed in kdenetwork:
status:	Incomplete → Invalid

Affects		Status	Importance	Assigned to	Milestone
	KDE Network	Invalid	High	kde-bugs #157316
	kdenetwork (Ubuntu)	Fix Released	Medium	Unassigned

Ubuntu
kdenetwork package

kopete-kde4 crashes when connecting to some Jabber servers

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntukdenetwork package

kopete-kde4 crashes when connecting to some Jabber servers

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
kdenetwork package