kopete crashed with SIGSEGV in memcpy()

Bug #271381 reported by Adam Szalkowski
22
Affects Status Importance Assigned to Milestone
KDE Network
Invalid
High
kdenetwork (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: kdenetwork

Installed Version of kopete: 4:4.1.1-0ubuntu2
Description: Ubuntu intrepid (development branch)
Release: 8.10

Kopete segfaults when connecting to an XMPP account (gmx.net, SSL, icq/msn/yahoo transports) right after establishing connection, fetching contacts and receiving a few status updates from contacts.
This is a fresh install with a fresh homedir and ampty ~/.kde

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/kopete
Package: kopete 4:4.1.1-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/kopete -caption Kopete
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdenetwork
StacktraceTop:
 memcpy () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libkdecore.so.5
 KNetwork::KBufferedSocket::slotWriteActivity ()
 KNetwork::KBufferedSocket::qt_metacall ()
 QMetaObject::activate () from /usr/lib/libQtCore.so.4
Title: kopete crashed with SIGSEGV in memcpy()
Uname: Linux 2.6.27-3-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Adam Szalkowski (adamsz) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:memcpy () from /lib/tls/i686/cmov/libc.so.6
KNetwork::Internal::KSocketBuffer::sendTo (this=0x96d6ee0,
KNetwork::KBufferedSocket::slotWriteActivity (this=0x98ca9b0)
KNetwork::KBufferedSocket::qt_metacall (this=0x98ca9b0,
QMetaObject::activate () from /usr/lib/libQtCore.so.4

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in kdenetwork:
importance: Undecided → Medium
Changed in kdenetwork:
importance: Medium → Low
status: New → Triaged
Changed in kdenetwork:
status: Unknown → Confirmed
Changed in kdenetwork:
status: Confirmed → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Should be fixed in KDE 4.2.

Changed in kdenetwork (Ubuntu):
status: Triaged → Fix Released
Changed in kdenetwork:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.