Bug 100528 - Kopete segfaults when I logout
Summary: Kopete segfaults when I logout
Status: RESOLVED DUPLICATE of bug 91288
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-01 10:54 UTC by Gleb Litvjak
Modified: 2005-03-03 12:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
The backtrace (3.11 KB, text/plain)
2005-03-02 13:32 UTC, Gleb Litvjak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gleb Litvjak 2005-03-01 10:54:48 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 3.4.3 20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7) 
OS:                Linux

Every time I logout, kopete segfaults. I cannot copy the backtrace, as the logout process continues, and the window disappears after a few seconds.
Comment 1 Will Stephenson 2005-03-01 23:40:22 UTC
Add 'sleep 99999' to the end of $KDEDIR/bin/startkde and copy the backtrace 
please.
Comment 2 Gleb Litvjak 2005-03-02 13:32:33 UTC
Created attachment 9916 [details]
The backtrace

Well, the sleep 99999 didn't help - the SIGSEGV window got killed , and I was
presented with a black screen, but I managed to save the backtrace. Don't know
if it is useful - I emerged kde without the debug USE flag. If it is necessary,
I could recompile with debug and nostrip and post the backtrace.

There is a similar closed bugreport - http://bugs.kde.org/show_bug.cgi?id=91288

Maybe it is connected with the issue I have.
Comment 3 Gleb Litvjak 2005-03-02 13:35:11 UTC
I just found out that kopete segfaults only when I am connected to jabber. If  kopete is running, but is not connected, it does not segfault on logout.
Comment 4 Will Stephenson 2005-03-03 12:56:10 UTC
Gleb, thank you for the backtrace and troubleshooting - with your information i can confirm that it still happens and is the same as 91288. 

*** This bug has been marked as a duplicate of 91288 ***