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

[Nikos Efthimiou]

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
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdenetwork
StacktraceTop:
 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

[Florian Reinhard (freinhard)]

Version: 0.60.82 (using Devel)
OS: Linux
Installed from: Compiled sources

plugins:
* KopeteTeX
* statistics
* history
* otr (quit the otr session since file transfer doesn't work with otr)

howto reproduce:
1) send a file to a jabber-contact
2) you get a progress window in systray, this one contains a stop-button, hit it

don't know if it matters whether the jabber-contact accepted the filetransfer or not

backtrace:
Anwendung: Kopete (kopete), Signal SIGSEGV
[Current thread is 0 (LWP 11246)]

Thread 3 (Thread 0xb2454b90 (LWP 11335)):
#0 0xb5d5d54a in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1 0xb6ea30ab in ?? () from /usr/lib/libQtCore.so.4
#2 0xb6ea3281 in ?? () from /usr/lib/libQtCore.so.4
#3 0xb6ea4e3c in ?? () from /usr/lib/libQtCore.so.4
#4 0xb6ea165a in ?? () from /usr/lib/libQtCore.so.4
#5 0xb5cde602 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#6 0xb5cdea8a in ?? () from /usr/lib/libglib-2.0.so.0
#7 0xb5cdef61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#8 0xb6ea1497 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#9 0xb6e7552a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#10 0xb6e756ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#11 0xb2f01e59 in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#12 0xb6d866ae in ?? () from /usr/lib/libQtCore.so.4
#13 0xb5e7550f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#14 0xb623e7ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xb2c55b90 (LWP 11336)):
#0 0xb806b430 in __kernel_vsyscall ()
#1 0xb5e79075 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb624c9ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libc.so.6
#3 0xb6d876f2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4 0xb7636532 in ?? () from /usr/lib/libQtNetwork.so.4
#5 0xb6d866ae in ?? () from /usr/lib/libQtCore.so.4
#6 0xb5e7550f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb623e7ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb58196c0 (LWP 11246)):
[KCrash Handler]
#6 0xb70a205c in KJob::setError (this=0xaffb950, errorCode=123) at /build/buildd/kde4libs-4.1.96/kdecore/jobs/kjob.cpp:234
#7 0xb7dbe121 in Kopete::Transfer::slotError (this=0xaffb950, error=123, errorText=@0xbfa6ac94) at /build/buildd/kdenetwork-4.1.96/kopete/libkopete/kopetetransfermanager.cpp:257
#8 0xb30812d1 in JabberFileTransfer::slotTransferError (this=0xaffbbe8, errorCode=2) at /build/buildd/kdenetwork-4.1.96/kopete/protocols/jabber/jabberfiletransfer.cpp:282
#9 0xb308508c in JabberFileTransfer::qt_metacall (this=0xaffbbe8, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfa6addc)
    at /build/buildd/kdenetwork-4.1.96/obj-i486-linux-gnu/kopete/protocols/jabber/jabberfiletransfer.moc:80
#10 0xb6e8ba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb6e8c7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb2dce803 in XMPP::FileTransfer::error (this=0xb0fea38, _t1=2) at /build/buildd/kdenetwork-4.1.96/obj-i486-linux-gnu/kopete/protocols/jabber/libiris/moc_filetransfer...

[Manolis-x (manolis-x)]

I have the same thing with a transfer of a pdf with MSN live

Application: Kopete (kopete), signal SIGSEGV
0x00007fc72fed7dc1 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 21139)]

Thread 2 (Thread 0x7fc7202ae950 (LWP 21241)):
#0 0x00007fc73175fdb9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007fc7319d16a3 in QWaitCondition::wait () from /usr/lib64/qt4/libQtCore.so.4
#2 0x00007fc732d71464 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#3 0x00007fc7319d0632 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#4 0x00007fc73175c007 in start_thread () from /lib/libpthread.so.0
#5 0x00007fc72ff0838d in clone () from /lib/libc.so.6
#6 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fc7356f3750 (LWP 21139)):
[KCrash Handler]
#5 0x00007fc731afdeaf in QObject::startTimer () from /usr/lib64/qt4/libQtCore.so.4
#6 0x00007fc734559c18 in Kopete::Transfer::slotProcessed (this=0x3340af0, bytes=415892)
    at /home/public/portage/tmp/portage/kde-base/kopete-4.2.0/work/kopete-4.2.0/kopete/libkopete/kopetetransfermanager.cpp:213
#7 0x00007fc720e1761e in WlmTransferManager::gotFileTransferProgress (this=0x1646370, conn=<value optimized out>, sessionID=@0x7fff3d845e14, transferred=@0x7fff3d845e08)
    at /home/public/portage/tmp/portage/kde-base/kopete-4.2.0/work/kopete-4.2.0/kopete/protocols/wlm/wlmtransfermanager.cpp:174
#8 0x00007fc720e195d7 in WlmTransferManager::qt_metacall (this=0x1646370, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff3d845dd0)
    at /home/public/portage/tmp/portage/kde-base/kopete-4.2.0/work/kopete_build/kopete/protocols/wlm/wlmtransfermanager.moc:88
#9 0x00007fc731b073f4 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007fc720e0481c in Callbacks::gotFileTransferProgress (this=0x3340af0, _t1=0x1a686e0, _t2=<value optimized out>, _t3=<value optimized out>)
    at /home/public/portage/tmp/portage/kde-base/kopete-4.2.0/work/kopete_build/kopete/protocols/wlm/wlmlibmsn.moc:291
#11 0x00007fc720e0485c in Callbacks::fileTransferProgress (this=0x3340af0, conn=0x3e8, sessionID=8517235, transferred=415892, total=72335920)
    at /home/public/portage/tmp/portage/kde-base/kopete-4.2.0/work/kopete-4.2.0/kopete/protocols/wlm/wlmlibmsn.cpp:587
#12 0x00007fc720bae97c in MSN::P2P::receiveP2PData (this=0x1a68750, conn=@0x1a686e0, packet=@0x7fff3d846360)
    at /home/public/portage/tmp/portage/net-libs/libmsn-4.0_beta4/work/libmsn-4.0-beta4/msn/p2p.cpp:314
#13 0x00007fc720baf32a in MSN::P2P::handleP2Pmessage (this=0x1a68750, conn=@0x1a686e0, args=@0x7fff3d8468b0, mime=<value optimized out>, body=<value optimized out>)
    at /home/public/portage/tmp/portage/net-libs/libmsn-4.0_beta4/work/libmsn-4.0-beta4/msn/p2p.cpp:145
#14 0x00007fc720b53827 in MSN::SwitchboardServerConnection::message_p2p (this=0x1a686e0, args=@0x7fff3d8468b0, mime=
        {static npos = 18446744073709551615, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x7fff3d8465d0 "\210\nS\004"}},
    body=<value optimized out>) at /home/public/portage/tmp/portage/net-libs/libmsn-4.0_beta4/work/libmsn-4.0-beta4/msn/switchboardserver...

[Apport retracing service (apport)]

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

[Dario Andres (andresbajotierra)]

The last backtrace seems a bit different.
Is this still happening with current versions ? Thanks

[Jonathan Thomas (echidnaman)]

Hi,
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.

[Jonathan Thomas (echidnaman)]

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!

[Dario Andres (andresbajotierra)]

*** Bug 183912 has been marked as a duplicate of this bug. ***

[Justin Zobel (justin-zobel)]

Thank you for the report, Florian.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.

[Bug-janitor (bug-janitor)]

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

[Bug-janitor (bug-janitor)]

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!