Bug 172186 - Kopete crash when receiving auth on startup
Summary: Kopete crash when receiving auth on startup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdenetwork
Version: 3
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-01 10:06 UTC by André Johansen
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: FC5
Clone Of:
Environment:
Last Closed: 2006-05-07 12:08:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Call stack (215.95 KB, text/plain)
2005-11-01 10:06 UTC, André Johansen 		no flags Details
Valgrind output (7.35 KB, text/plain)
2005-11-01 12:25 UTC, André Johansen 		no flags Details
View All

Description André Johansen 2005-11-01 10:06:29 UTC 
Description of problem:  
A person I've got on my ICQ list has asked for authorisation while I was  
offline.  Whenever I start Kopete now, I get about 50 authorisation windows  
opened.  Closing any of them (ok, cancel, esc, enter) crashes Kopete.  I'll  
attach a call-stack from the KDE crash handler.  
  
Version-Release number of selected component (if applicable):  
Qt: 3.3.4  
KDE: 3.4.2-0.fc3.2 Red Hat  
Kopete: 0.10.3  
kdenetwork-3.4.2-0.fc3.1  
  
How reproducible:  
I've not attempted to reproduce this, but it happens almost all the time for 
me now. 
  
Steps to Reproduce:  
1. Start Kopete (from menu or command line)  
2. Close one or more of the authorisation windows (e.g. Ok or Cancel)  
3. Crash
Comment 1 André Johansen 2005-11-01 10:06:30 UTC 
Created attachment 120598 [details]
Call stack
Comment 2 André Johansen 2005-11-01 12:25:57 UTC 
Created attachment 120599 [details]
Valgrind output

The crash seems to be caused by double freeing of heap memory; running Kopete
under Valgrind shows this.
Comment 3 André Johansen 2005-11-01 12:47:02 UTC 
It seems Kopete from the current KDE 3.5 SVN has fixed this problem, so 
pushing out KDE 3.5 (when released) will likely fix this bug.
Note You need to log in before you can comment on or make changes to this bug.