kopete crashes with jabber account after closing

Bug #63736 reported by Martin Nowack
2
Affects Status Importance Assigned to Milestone
KDE Network
Won't Fix
High
kdenetwork (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

I use kopete on several machines one with edgy and two with dapper (kopete-0.12.2).

I've got always the problem, when I use kopete and I use it with jabber, I can communicate well. But after closing kopete it crashes. It happens in the destructor of jabberaccount.cpp.

Here the backtrace:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240553808 (LWP 7313)]
[KCrash handler]
#6 0x00000000 in ?? ()
#7 0xb5bb5aeb in ~JabberAccount (this=0x82d5db8) at jabberaccount.cpp:130
#8 0xb68f8e68 in QObject::event (this=0x82d5db8, e=0x83b6240)
    at kernel/qobject.cpp:750
#9 0xb6890a98 in QApplication::internalNotify (this=0xbff91e04,
    receiver=0x82d5db8, e=0x83b6240) at kernel/qapplication.cpp:2635
#10 0xb68928c7 in QApplication::notify (this=0xbff91e04, receiver=0x82d5db8,
    e=0x83b6240) at kernel/qapplication.cpp:2358
#11 0xb7042062 in KApplication::notify () from /usr/lib/libkdecore.so.4
#12 0xb6823389 in QApplication::sendEvent (receiver=0x82d5db8,
    event=0x83b6240) at ../include/qapplication.h:520
#13 0xb6891ad0 in QApplication::sendPostedEvents (receiver=0x0, event_type=0)
    at kernel/qapplication.cpp:3299
#14 0xb6891bd8 in QApplication::sendPostedEvents ()
    at kernel/qapplication.cpp:3210
#15 0xb6837391 in QEventLoop::processEvents (this=0x8198908, flags=4)
    at kernel/qeventloop_x11.cpp:202
#16 0xb68ab16e in QEventLoop::enterLoop (this=0x8198908)
    at kernel/qeventloop.cpp:198
#17 0xb68aaf7e in QEventLoop::exec (this=0x8198908)
    at kernel/qeventloop.cpp:145
#18 0xb6892641 in QApplication::exec (this=0xbff91e04)
    at kernel/qapplication.cpp:2758
#19 0x080733f6 in main (argc=0, argv=0x0) at main.cpp:107

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

I cant reproduce this.

Does this happen consistently, or only once?

Also, what happens if you move ~/.kde/share/config/kopete* and ~/.kde/share/apps/kopete out of the way? Does this bug still occur?

Changed in kopete:
status: Unconfirmed → Needs Info
Revision history for this message
Martin Nowack (martin-nowack) wrote :

OK, I checked again.
I tried it with several new configuration and on several machines. It happens under edgy and dapper.
I've found the problem, seams to be upstream.
A more detailed explanation: I tried to use the transport mechanism of jabber to get an ICQ connection over jabber. With this enabled kopete crashes, without kopete won't crash.

HowTo for ICQ-transport ;)
1. Your provider should have this service (e.g. amessage.info)
2. Connect to your provider (you should be online, not invisible)
3. Click the bulb of your jabber-account
4. Click Services in the context menue
5. "Query Server" (for me it is amessage.info) -> icq.amessage.info gets listed
6. Select your icq-transport and click the Register button
7. Enter your icq number and password

A new symbol in your account list appears (the jabber bulb combined with the icq flower). Now you can see your icq contacts through jabber :)

But now, if you close kopete it crashes, even if you didn't connect.
If you remove this service account kopete will crash a last time after closing. After that, kopete won't do this.

Revision history for this message
Andres Mujica (andres.mujica) wrote :

i've got this same issue but with IRC protocol as stated on this bug report

56531

https://launchpad.net/distros/ubuntu/+source/kdenetwork/+bug/56531

Changed in kopete:
status: Needs Info → Confirmed
Changed in kdenetwork:
status: Unknown → Unconfirmed
Changed in kdenetwork:
status: New → Invalid
Changed in kdenetwork:
status: Invalid → Unknown
importance: Undecided → Low
status: Confirmed → Triaged
Changed in kdenetwork:
status: Unknown → New
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Qt issue, should be resolved in 9.04.

Changed in kdenetwork:
status: New → Unknown
Changed in kdenetwork (Ubuntu):
status: Triaged → Fix Released
Changed in kdenetwork:
status: Unknown → Fix Released
Changed in kdenetwork:
status: Fix Released → Won't Fix
Changed in kdenetwork:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.