Bug 228293 - Pushing multiple files to host using kbluetooth pops up many system tray windows, then crashes [KJob::emitResult. ObexServerSession::disconnect, ObexServerSessionFileTransfer::doKill, KJob::kill]
Summary: Pushing multiple files to host using kbluetooth pops up many system tray wind...
Status: RESOLVED DUPLICATE of bug 270702
Alias: None
Product: kbluetooth
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 0.4
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
: 249252 251666 254482 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-24 12:39 UTC by Roman Fietze
Modified: 2011-04-11 19:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screen dump of system tray running job notifications. (140.13 KB, image/png)
2010-02-24 12:42 UTC, Roman Fietze 		Details
New crash information added by DrKonqi (4.65 KB, text/plain)
2010-10-15 10:32 UTC, Bruno Friedmann 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Fietze 2010-02-24 12:39:03 UTC 
Application: kbluetooth (0.4)
KDE Platform Version: 4.4.00 (KDE 4.4.0) "release 2"
Qt Version: 4.6.2
Operating System: Linux 2.6.31.12-0.1-default x86_64
Distribution (Platform): openSUSE RPMs

-- Information about the crash:
Sending multiple files from a mobile via BT to the host running kbluetooth opens many running job windows of the system tray notification system. When I see it correctly there is more than one running job notification per sent file. See the attachment for that.

Those running job notifications are never closed, allthough all the files are received properly. When I then try to get rid of those notifications using the stop button (the square as on a cassette deck), kbluetooth crashes.

I checked other bug reports, many just don't match (e.g. kbluetooth crashing before even receiving any data) or are marked resolved and fixed.


The crash can be reproduced every time.

 -- Backtrace:
Application: KBluetooth (kbluetooth), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f2b3e276721 in KJob::emitResult() () from /usr/lib64/libkdecore.so.5
#6  0x00000000004290e7 in ObexServerSession::disconnect (this=0x8273d0) at /usr/src/debug/kbluetooth-0.4/src/obexserver/obexserversession.cpp:68
#7  0x000000000042a357 in ObexServerSessionFileTransfer::doKill (this=0x965b90) at /usr/src/debug/kbluetooth-0.4/src/obexserver/obexserversessionfiletransfer.cpp:110
#8  0x00007f2b3e2768e9 in KJob::kill(KJob::KillVerbosity) () from /usr/lib64/libkdecore.so.5
#9  0x00007f2b3fbc8ac5 in KUiServerJobTracker::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdeui.so.5
#10 0x00007f2b3dc4f78f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#11 0x00007f2b3fdb7188 in ?? () from /usr/lib64/libkdeui.so.5
#12 0x00007f2b3df7622e in ?? () from /usr/lib64/libQtDBus.so.4
#13 0x00007f2b3df81e6f in ?? () from /usr/lib64/libQtDBus.so.4
#14 0x00007f2b3dc4c6c9 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#15 0x00007f2b3e812e1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f2b3e8193fb in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f2b3fc0e446 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#18 0x00007f2b3dc3c98c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007f2b3dc3f107 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#20 0x00007f2b3dc66373 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007f2b39f60dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f2b39f647b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f2b39f648e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f2b3dc65eb3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007f2b3e8c151e in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007f2b3dc3b2a2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f2b3dc3b67c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f2b3dc3f3cb in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#29 0x000000000040f1c1 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kbluetooth-0.4/src/main.cpp:71

Reported using DrKonqi
Comment 1 Roman Fietze 2010-02-24 12:42:52 UTC 
Created attachment 41054 [details]
Screen dump of system tray running job notifications.

Correction of the bug report text: there is only one notification per file, but while receiving the data it seems the progress bar of all files already done is reset when a new file starts.
Comment 2 Dario Andres 2010-02-24 22:41:39 UTC 
According to the recently fixed bug 225924 and bug 220145 this should work in a recent version.
@Alex: are those the same issue ?
Regards
Comment 3 Bruno Friedmann 2010-10-15 10:32:24 UTC 
Created attachment 52528 [details]
New crash information added by DrKonqi

kbluetooth (0.4) on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.7.0

- What I was doing when the application crashed:
I send over bluetooth 3 files, kbluetooth work and notifications open 3 popups.
The first is marked done, and the two others are marked as running, with the slide transfert at 100%. ( In fact files are already transferred and good on filesystem )

If you want to close the popup notification, you have to click the square stop.
If you do that, you ended to a crash, kbluetooth closed.

-- Backtrace (Reduced):
#6  KJob::emitResult (this=0xaca1a0) at /usr/src/debug/kdelibs-4.5.2/kdecore/jobs/kjob.cpp:305
#7  0x0000000000426277 in ObexServerSession::disconnect (this=0xa53a70) at /usr/src/debug/kbluetooth-0.4.2/src/obexserver/obexserversession.cpp:69
#8  0x0000000000427e37 in ObexServerSessionFileTransfer::doKill (this=0xb1fbc0) at /usr/src/debug/kbluetooth-0.4.2/src/obexserver/obexserversessionfiletransfer.cpp:120
#9  0x00007fc119f7b981 in KJob::kill (this=0xb1fbc0, verbosity=KJob::EmitResult) at /usr/src/debug/kdelibs-4.5.2/kdecore/jobs/kjob.cpp:106
#10 0x00007fc11b944b29 in KUiServerJobTracker::Private::_k_killJob (this=0xa2d270) at /usr/src/debug/kdelibs-4.5.2/kdeui/jobs/kuiserverjobtracker.cpp:59
Comment 4 Dario Andres 2010-11-18 20:51:00 UTC 
[Comment from a bug triager]
From bug 249252:
-- Information about the crash:
Just sending multiple file to pc with kde 4.4.4 opensuse 11.3
knotifiy leave open with 10 task open, even if files were correctly transfered

From bug 254482:
- What I was doing when the application crashed:
closing one of those transfert marked as running done at 100% lead to this
crash.

From bug 251666:
-- Information about the crash:
When I send multiples files from the phone to kbluetooth, it open a new poppup
notification for each files ( so 22 files are in copy ), but when a file
transfert has ended a new notification appear for the 22 files too, leading to
multiple of multiple notification.
Then I click on the close transfert of one of them, and it crash.
Comment 5 Dario Andres 2010-11-18 20:51:06 UTC 
*** Bug 249252 has been marked as a duplicate of this bug. ***
Comment 6 Dario Andres 2010-11-18 20:51:09 UTC 
*** Bug 254482 has been marked as a duplicate of this bug. ***
Comment 7 Dario Andres 2010-11-18 20:51:11 UTC 
*** Bug 251666 has been marked as a duplicate of this bug. ***
Comment 8 Lamarque V. Souza 2011-04-11 19:45:43 UTC 

*** This bug has been marked as a duplicate of bug 270702 ***