Bug 251666 - Receiving multiple files from bluetooth phone open multiple pop-up notification
Summary: Receiving multiple files from bluetooth phone open multiple pop-up notification
Status: RESOLVED DUPLICATE of bug 228293
Alias: None
Product: kbluetooth
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.4
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-18 14:49 UTC by Bruno Friedmann
Modified: 2010-11-18 20:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (4.39 KB, text/plain)
2010-09-19 15:06 UTC, Bruno Friedmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Friedmann 2010-09-18 14:49:52 UTC
Application: kbluetooth (0.4)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 3"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.4-0.1-desktop i686
Distribution: "openSUSE 11.3 (i586)"

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


The crash can be reproduced every time.

 -- Backtrace:
Application: KBluetooth (kbluetooth), signal: Segmentation fault
[KCrash Handler]
#6  0xb631880a in KJob::emitResult() () from /usr/lib/libkdecore.so.5
#7  0x0806ce4a in ObexServerSession::disconnect (this=0x83ebc48) at /usr/src/debug/kbluetooth-0.4.2/src/obexserver/obexserversession.cpp:69
#8  0x0806ec1a in ObexServerSessionFileTransfer::doKill (this=0x827b4b0) at /usr/src/debug/kbluetooth-0.4.2/src/obexserver/obexserversessionfiletransfer.cpp:120
#9  0xb6318888 in KJob::kill(KJob::KillVerbosity) () from /usr/lib/libkdecore.so.5
#10 0xb72adb7f in KUiServerJobTracker::Private::_k_killJob (this=0x847b7f0) at /usr/src/debug/kdelibs-4.4.4/kdeui/jobs/kuiserverjobtracker.cpp:58
#11 0xb72adbff in KUiServerJobTracker::qt_metacall (this=0x83bc0c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfebd9ac)
    at /usr/src/debug/kdelibs-4.4.4/build/kdeui/kuiserverjobtracker.moc:100
#12 0xb60feefd in QMetaObject::metacall (object=0x83bc0c0, cl=QMetaObject::InvokeMetaMethod, idx=25, argv=0xbfebd9ac) at kernel/qmetaobject.cpp:237
#13 0xb610dfe8 in QMetaObject::activate (sender=0x8488688, m=0xb74944c4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#14 0xb73e2655 in OrgKdeJobViewInterface::cancelRequested (this=0x8488688) at /usr/src/debug/kdelibs-4.4.4/build/kdeui/jobviewiface.moc:119
#15 0xb73e2c08 in OrgKdeJobViewInterface::qt_metacall (this=0x8488688, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfebdc6c) at /usr/src/debug/kdelibs-4.4.4/build/kdeui/jobviewiface.moc:96
#16 0xb6233a37 in QDBusConnectionPrivate::deliverCall (this=0x80a0060, object=0x8488688, msg=..., metaTypes=..., slotIdx=40) at qdbusintegrator.cpp:904
#17 0xb6241536 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8404970, object=0x8488688) at qdbusintegrator_p.h:101
#18 0xb610b93f in QObject::event (this=0x8488688, e=0x8404970) at kernel/qobject.cpp:1248
#19 0xb6623c64 in QApplicationPrivate::notify_helper (this=0x80a8b68, receiver=0x8488688, e=0x8404970) at kernel/qapplication.cpp:4302
#20 0xb662bbf7 in QApplication::notify (this=0xbfebe598, receiver=0x8488688, e=0x8404970) at kernel/qapplication.cpp:3706
#21 0xb71ef9d1 in KApplication::notify (this=0xbfebe598, receiver=0x8488688, event=0x8404970) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302
#22 0xb60f8e0e in QCoreApplication::notifyInternal (this=0xbfebe598, receiver=0x8488688, event=0x8404970) at kernel/qcoreapplication.cpp:726
#23 0xb60fc9b4 in sendEvent (receiver=0x0, event_type=0, data=0x80884f0) at kernel/qcoreapplication.h:215
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x80884f0) at kernel/qcoreapplication.cpp:1367
#25 0xb60fcb9c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1260
#26 0xb612483d in sendPostedEvents (s=0x80aab10) at kernel/qcoreapplication.h:220
#27 postEventSourceDispatch (s=0x80aab10) at kernel/qeventdispatcher_glib.cpp:276
#28 0xb5603b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb5604350 in ?? () from /usr/lib/libglib-2.0.so.0
#30 0xb560460e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#31 0xb6124d4b in QEventDispatcherGlib::processEvents (this=0x808bf00, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#32 0xb66d419a in QGuiEventDispatcherGlib::processEvents (this=0x808bf00, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0xb60f811d in QEventLoop::processEvents (this=0xbfebe434, flags=...) at kernel/qeventloop.cpp:149
#34 0xb60f8319 in QEventLoop::exec (this=0xbfebe434, flags=...) at kernel/qeventloop.cpp:201
#35 0xb60fcc70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#36 0xb6621164 in QApplication::exec () at kernel/qapplication.cpp:3581
#37 0x08054b69 in main (argc=) at /usr/src/debug/kbluetooth-0.4.2/src/main.cpp:71

This bug may be a duplicate of or related to bug 249252, bug 228293.

Possible duplicates by query: bug 249252, bug 228293.

Reported using DrKonqi
Comment 1 Bruno Friedmann 2010-09-19 15:06:13 UTC
Created attachment 51805 [details]
New crash information added by DrKonqi

Exactly same manipulation like in #215666
Transfert ended correctly after the 11 files received, but there's 12 tasks running even if their transfert ended correctly.
Close one clicking the stop button lead to this crash
Comment 2 Dario Andres 2010-11-18 20:51:11 UTC
[Comment from a bug triager]
This issue is being tracked at bug 228293. Merging. Thanks

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