Bug 168626 - kopete crashes on sending ICQ message
Summary: kopete crashes on sending ICQ message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kdenetwork
Version: 4
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-18 15:11 UTC by Leonid Zeitlin
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-07 12:02:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Backtrace of the crash (2.72 KB, text/plain)
2005-09-18 15:13 UTC, Leonid Zeitlin 		no flags Details
excerpt from kopete debug log (4.99 KB, text/plain)
2005-09-18 15:16 UTC, Leonid Zeitlin 		no flags Details
View All

Description Leonid Zeitlin 2005-09-18 15:11:49 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.2 (like Gecko)

Description of problem:
Kopete often crashes when sending ICQ message. When I press "send" button, a 
message box "An unknown error has occurred and the connection has been closed" 
is shown, and then the application crashes. Backtrace and kopete debug log are 
attached. This happens often, but not always. 

Version-Release number of selected component (if applicable):
kdenetwork-3.4.2-0.fc4.1

How reproducible:
Sometimes

Steps to Reproduce:
1. Start kopete 
2. Send a few messages to any ICQ contact 
 
   

Additional info:
Comment 1 Leonid Zeitlin 2005-09-18 15:13:45 UTC 
Created attachment 118946 [details]
Backtrace of the crash
Comment 2 Leonid Zeitlin 2005-09-18 15:16:37 UTC 
Created attachment 118947 [details]
excerpt from kopete debug log
Comment 3 Leonid Zeitlin 2005-09-18 15:18:13 UTC 
BTW, this never happenned to me in kdenetwork-3.4.1. Started when I upgraded 
to 3.4.2.
Comment 4 Than Ngo 2006-05-07 12:02:45 UTC 
Could you please try new kde-3.5.2 from FC4-update. Please reopen it again if this
problem still appears. Thanks for your report.
Note You need to log in before you can comment on or make changes to this bug.