Bug 154389 - Kopete freezes while opening chat window for Jabber contacts
Summary: Kopete freezes while opening chat window for Jabber contacts
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-20 20:00 UTC by David Hajek
Modified: 2008-12-30 02:13 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Hajek 2007-12-20 20:00:03 UTC
Version:           0.12.7 (using KDE 3.5.8, Arch Linux)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.23-ARCH

I don't have much description. I'm using jabber.cz mainly for ICQ transport. Yesterday I added a Jabber guy. We talked for a bit. Today it stopped working - clicking him in contacts freezes Kopete only solution being killing it. I'd like to be more descriptive but I'm new to bug tracking on linux so any advices are welcome. Thanx
Comment 1 David Hajek 2007-12-20 20:04:39 UTC
By the way I also cannot remove contact groups - they reappear after restarting - and sometimes Kopete crashes while doing online->offline->online status change sequence.
Comment 2 David Hajek 2007-12-21 21:08:34 UTC
Well, it freezes only when trying to open chat window for one specific contact. I tried deleting/readding him. Still experiencing freezing.
Comment 3 Alan Jones 2008-12-29 09:54:50 UTC
Hi David,

Thanks for the report. Would you be able to confirm repro with this in the 0.50 (kde4) series, please? Also if possible generating a backtrace would be great. You may need to do this with gdb by hand given it freezes, and it might not work.

To do it fire up kopete. And get everything in place to just before you'd make it freeze. Open up a konsole/terminal. Run gdb (assuming you have it installed). Attach to the pid of kopete. "ps ax | grep kopete" will show you what the pid is. Say it's 18410 then you'd run "attach 18410" in gdb. Then "continue" in gdb. Each of these commands is followed by enter btw. Then do what you do that makes it freeze in kopete. Then run "backtrace" in gdb and send the output.

Cheers,

Alan.
Comment 4 David Hajek 2008-12-29 19:14:20 UTC
(In reply to comment #3)
> Hi David,
> 
> Thanks for the report. Would you be able to confirm repro with this in the 0.50
> (kde4) series, please? Also if possible generating a backtrace would be great.
> You may need to do this with gdb by hand given it freezes, and it might not
> work.
> 
> To do it fire up kopete. And get everything in place to just before you'd make
> it freeze. Open up a konsole/terminal. Run gdb (assuming you have it
> installed). Attach to the pid of kopete. "ps ax | grep kopete" will show you
> what the pid is. Say it's 18410 then you'd run "attach 18410" in gdb. Then
> "continue" in gdb. Each of these commands is followed by enter btw. Then do
> what you do that makes it freeze in kopete. Then run "backtrace" in gdb and
> send the output.
> 
> Cheers,
> 
> Alan.
> 

Hi Alan,

it's been a long time, almost a year. I switched to the tiling window managers like awesome since then. So I no longer can do a backtrace of Kopete, sorry.

David
Comment 5 Alan Jones 2008-12-30 02:13:31 UTC
Closing bug as we have no repro.

Cheers,

Alan.