Bug 172186

Summary: Kopete crash when receiving auth on startup
Product: [Fedora] Fedora Reporter: André Johansen <andrejoh>
Component: kdenetworkAssignee: Than Ngo <than>
Status: CLOSED CURRENTRELEASE QA Contact: Ben Levenson <benl>
Severity: high Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: FC5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-07 12:08:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Call stack
none
Valgrind output none

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.