Bug 247668 - Bluetooth-monolithic crashed while using obexftp command
Summary: Bluetooth-monolithic crashed while using obexftp command
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: bluetooth (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-13 17:35 UTC by Andrey Borzenkov
Modified: 2010-10-13 23:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Borzenkov 2010-08-13 17:35:44 UTC
Application: bluedevil-monolithic (0.1)
KDE Platform Version: 4.5.00 (KDE 4.5.0)
Qt Version: 4.7.0
Operating System: Linux 2.6.35.1-desktop-1mnb x86_64
Distribution: "Mandriva Linux 2010.1"

-- Information about the crash:
- What I was doing when the application crashed:

I was testing obexftp access to phone. I disconnected phone from BD via Manage Devices and several times called obexftp. At some point BD crashed

-- Backtrace:
Application: Bluetooth (bluedevil-monolithic), signal: Segmentation fault
[KCrash Handler]
#6  Private (this=0x7fffa36ee950, p=...) at kernel/qvariant.h:360
#7  QVariant::QVariant (this=0x7fffa36ee950, p=...) at kernel/qvariant.cpp:1419
#8  0x00007fc24d872794 in QAction::data (this=<value optimized out>) at kernel/qaction.cpp:1198
#9  0x0000000000407670 in Monolithic::addDevice (this=0x15866d0, device=0x15e6a00) at /usr/src/debug/bluedevil-0.1/src/monolithic/monolithic.cpp:471
#10 0x0000000000404304 in Monolithic::qt_metacall (this=0x15866d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa36eeb70)
    at /usr/src/debug/bluedevil-0.1/build/src/monolithic/moc_monolithic.cpp:112
#11 0x00007fc24cc7beb7 in QMetaObject::activate (sender=0x159c2f0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3272
#12 0x00007fc24e39b382 in BlueDevil::Adapter::deviceCreated(BlueDevil::Device*) () from /usr/lib64/libbluedevil.so.1
#13 0x00007fc24e39bd16 in BlueDevil::Adapter::Private::_k_deviceCreated(QDBusObjectPath const&) () from /usr/lib64/libbluedevil.so.1
#14 0x00007fc24e3a1788 in BlueDevil::Adapter::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libbluedevil.so.1
#15 0x00007fc24cc7beb7 in QMetaObject::activate (sender=0x159c790, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3272
#16 0x00007fc24e3aa3a2 in OrgBluezAdapterInterface::DeviceCreated(QDBusObjectPath const&) () from /usr/lib64/libbluedevil.so.1
#17 0x00007fc24e3ab7ac in OrgBluezAdapterInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libbluedevil.so.1
#18 0x00007fc24cfb8ede in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>)
    at qdbusintegrator.cpp:909
#19 0x00007fc24cfc3b7f in QDBusCallDeliveryEvent::placeMetaCall (this=0x159f128, object=0x22000000d9) at qdbusintegrator_p.h:103
#20 0x00007fc24cc7662e in QObject::event (this=0x159c790, e=0x7fffa36ee950) at kernel/qobject.cpp:1211
#21 0x00007fc24d879dec in QApplicationPrivate::notify_helper (this=0x1470d30, receiver=0x159c790, e=0x15ddc60) at kernel/qapplication.cpp:4389
#22 0x00007fc24d87fffd in QApplication::notify (this=0x7fffa36efe20, receiver=0x159c790, e=0x15ddc60) at kernel/qapplication.cpp:4270
#23 0x00007fc24e7dc3ae in KApplication::notify (this=0x7fffa36efe20, receiver=0x159c790, event=0x15ddc60) at /usr/src/debug/kdelibs-4.5.0/kdeui/kernel/kapplication.cpp:310
#24 0x00007fc24cc641ec in QCoreApplication::notifyInternal (this=0x7fffa36efe20, receiver=0x159c790, event=0x15ddc60) at kernel/qcoreapplication.cpp:732
#25 0x00007fc24cc67fe2 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x14404d0) at kernel/qcoreapplication.h:215
#26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x14404d0) at kernel/qcoreapplication.cpp:1373
#27 0x00007fc24cc907b3 in sendPostedEvents (s=0x14735a0) at kernel/qcoreapplication.h:220
#28 postEventSourceDispatch (s=0x14735a0) at kernel/qeventdispatcher_glib.cpp:277
#29 0x00007fc24980a700 in g_main_dispatch (context=0x14734c0) at gmain.c:2119
#30 g_main_context_dispatch (context=0x14734c0) at gmain.c:2672
#31 0x00007fc24980e648 in g_main_context_iterate (context=0x14734c0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2750
#32 0x00007fc24980e7fc in g_main_context_iteration (context=0x14734c0, may_block=1) at gmain.c:2813
#33 0x00007fc24cc902f3 in QEventDispatcherGlib::processEvents (this=0x143ffa0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#34 0x00007fc24d92a78e in QGuiEventDispatcherGlib::processEvents (this=0x7fffa36ee950, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#35 0x00007fc24cc62f12 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#36 0x00007fc24cc632fc in QEventLoop::exec (this=0x7fffa36efd90, flags=) at kernel/qeventloop.cpp:201
#37 0x00007fc24cc68279 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#38 0x000000000040485e in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/bluedevil-0.1/src/monolithic/main.cpp:39

Reported using DrKonqi
Comment 1 Christoph Feck 2010-08-13 17:42:17 UTC
NB: I had to change the status from UNCONFIRMED to NEW when reassigning. It said: You are not allowed to change the bug status from UNCONFIRMED to UNCONFIRMED.
Comment 2 Rafael Fernández López 2010-08-17 14:55:16 UTC
Please retry again with new version (or compile from sources). Fixed upstream: bluedevil version: e76495e43ac3c5258c858ac0a0fb9d71d1a6a565. libbluedevil version: e4e5de32fcc88fc80e5da66b037d92d7fd611d0b.
Comment 3 Alex Fiestas 2010-10-13 23:02:30 UTC
I'm going to close this bug because of feedback lacking.

If you can reproduce the bug feel free to reopen the bug.

Thanks for testing and reporting!