------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=122269
------- Additional Comments From daniel ekloef se 2006-03-11 11:22 -------
Created an attachment (id=15049)
--> (http://bugs.kde.org/attachment.cgi?id=15049&action=view)
debug output before crash
Here is the log-output after updating to r517492.
I'm getting more convinced that it is related to the ICQ-transport, at least in
my case. Some observations I have made:
1. Before the crash, the ICQ-transport instance is freed. Some time later, a
response is coming from the ICQ-transport on the jabber server. I don't know
how these things are handled in kopete, but I never see the MSN-transport being
freed (and I've never seen any crashes in it either).
2. At one occasion I actually managed to start kopete and login without getting
a crash. However, the ICQ-transport was offline. When I tried to set
availability to online, it complained and said I have to be connected (which I
was, all my jabber- and MSN-contacts were functioning). What's even more
strange is that kopete seemed to think I had a second jabber-account. This
account was named jabber.dk/registered. I assume the ICQ-transport was somehow
connected to this account. Naturally, I could not log in on this second
jabber-account.
3. Often the account-icons on the status-bar is completely messed up; the
ICQ-transport icon can be invisible while the ICQ popup menu is accessible via
the jabber-account icon; the jabber popup menu is then accessible from where
the ICQ-transport icon should have been (where it's just an empty space
instead). I realize this may not have anything at all to do with this bug, but
then again, maybe it has.
Since you haven't been able to reproduce this, let me know if you want me to
look for something particular.
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
