kopete crashed with SIGSEGV in Kopete::Transfer::slotProcessed()

Bug #330222 reported by Nikos Efthimiou on 2009-02-16
Affects Status Importance Assigned to Milestone
KDE Network
kdenetwork (Ubuntu)

Bug Description

Binary package hint: kdenetwork

The information widget stuck without any abnormal use, while I was trying to send a doc file...

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/kopete
Package: kopete 4:4.2.0-0ubuntu3
ProcCmdline: kopete -session 1015110a146140000123480536100000038050025_1234806167_781052
Signal: 11
SourcePackage: kdenetwork
 Kopete::Transfer::slotProcessed ()
 ?? () from /usr/lib/kde4/kopete_wlm.so
 ?? () from /usr/lib/kde4/kopete_wlm.so
 QMetaObject::activate ()
 ?? () from /usr/lib/kde4/kopete_wlm.so
Title: kopete crashed with SIGSEGV in Kopete::Transfer::slotProcessed()
Uname: Linux 2.6.28-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

StacktraceTop:WlmTransferManager::gotFileTransferProgress (
WlmTransferManager::qt_metacall (this=0x2ffe630,
QMetaObject::activate ()
Callbacks::gotFileTransferProgress (this=0x39208a0,
Callbacks::fileTransferProgress (this=0x39208a0,

Changed in kdenetwork:
importance: Undecided → Medium
visibility: private → public
Changed in kdenetwork (Ubuntu):
status: New → Triaged
Changed in kdenetwork:
status: Unknown → Confirmed
Jonathan Thomas (echidnaman) wrote :

We were wondering if this was still an issue for you in the final version of Kubuntu 9.04, or with KDE 4.2.4 (http://www.kubuntu.org/news/kde-4.2.4)
Thanks in advance.

Changed in kdenetwork (Ubuntu):
importance: Medium → Low
status: Triaged → Incomplete
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdenetwork (Ubuntu):
status: Incomplete → Invalid
Changed in kdenetwork:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  Edit
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.