Bug 198191 - kbluetooth4 crashes when receiving files from mobile phone
Summary: kbluetooth4 crashes when receiving files from mobile phone
Status: RESOLVED FIXED
Alias: None
Product: kbluetooth
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.4
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-28 17:59 UTC by Ciaran Farrell
Modified: 2010-01-31 22:16 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ciaran Farrell 2009-06-28 17:59:33 UTC 
Application that crashed: kbluetooth4
Version of the application: 0.3
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) "release 138"
Qt Version: 4.5.1
Operating System: Linux 2.6.27.23-0.1-default x86_64

What I was doing when the application crashed:
On the mobile phone I choose "send file over bluetooth" and then choose the device (my desktop computer). I click on "send" and on the desktop I get a pop-up prompt "receive files over bluetooth?".

I click on "OK" and a progress bar is displayed for a second or two. Then, the crash dialog appears and tells me there has been a floating point exception. Thus, I complete the bug report process in the crash dialog.

 -- Backtrace:
Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4), signal: Floating point exception
[KCrash Handler]
#5  0x000000000040d35b in KBlueTray::slotTransferProgress (this=0x7fffecb03da0, val=393) at /usr/src/debug/kdebluetooth4-0.3/src/trayicon.cpp:409
#6  0x000000000040ac44 in KBlueTray::qt_metacall (this=0x7fffecb03da0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffecb030b0)
    at /usr/src/debug/kdebluetooth4-0.3/build/src/moc_trayicon.cpp:157
#7  0x00007f36e2545c22 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#8  0x000000000040a4f0 in ObexServerSession::transferProgress (this=0x7fffecb02f50, _t1=393) at /usr/src/debug/kdebluetooth4-0.3/build/src/moc_obexserversession.cpp:133
#9  0x000000000040a8f7 in ObexServerSession::qt_metacall (this=0x831f80, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffecb03380)
    at /usr/src/debug/kdebluetooth4-0.3/build/src/moc_obexserversession.cpp:100
#10 0x00007f36e284a394 in ?? () from /usr/lib64/libQtDBus.so.4
#11 0x00007f36e2851fef in ?? () from /usr/lib64/libQtDBus.so.4
#12 0x00007f36e25402b8 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#13 0x00007f36e178a78d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007f36e1792a2a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007f36e403504b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#16 0x00007f36e253015c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#17 0x00007f36e2530dda in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#18 0x00007f36e2559c13 in ?? () from /usr/lib64/libQtCore.so.4
#19 0x00007f36dd9c50fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f36dd9c88cd in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f36dd9c8a8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f36e255989f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#23 0x00007f36e1821b0f in ?? () from /usr/lib64/libQtGui.so.4
#24 0x00007f36e252e9f2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007f36e252edbd in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f36e25310a4 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#27 0x000000000040b8cf in main (argc=3, argv=0x7fffecb04108) at /usr/src/debug/kdebluetooth4-0.3/src/main.cpp:74

Reported using DrKonqi
Comment 1 Alex Fiestas 2009-09-23 20:18:16 UTC 
Hi, can you test if you can reproduce this bug with 0.4 version?

Thanks!
Comment 2 Alex Fiestas 2009-11-04 17:32:18 UTC 
We got no answer here, so I'm not going to move it to the new product.

I'll do when I see some activity here.
Comment 3 Ciaran Farrell 2009-11-04 17:58:40 UTC 
I couldn't install version 0.4 until just now - and at that, from some person's home repository on the openSUSE build service.

Anyhow, I got 0.4 installed, and it successfully starts and minimizes itself to the system tray. When I repeat the steps from #1 I get an obex error:
org.openobex.Error.LinkError

The phone can see the PC and the PC can see the phone, and I managed to successfully pair both using the bluetooth-setup from Gnome.

I'll try to get the past the obex error in order to test if the actual crash occurs.
Comment 4 Alex Fiestas 2009-11-04 18:25:03 UTC 
Moved to the new product.

Can you test if you can do the steps from #1 using another bluetooth software like blueman?

Thanks!
Comment 5 Alex Fiestas 2009-11-09 18:55:28 UTC 
I've fixed a few crash that may be related with yours, can you test the last svn version of kbluetooth? you can get it by executing:
svn co svn://anonsvn.kde.org/home/kde/trunk/playground/network/kbluetooth/

Thanks!

Ps: What distro are you using?
Comment 6 Ciaran Farrell 2009-11-09 21:37:39 UTC 
I'll try that version. Using openSUSE 11.2. I tried bluman, but though it installed from the buildservice, it wouldn't run because of unmet python dependencies.
Comment 7 Ciaran Farrell 2009-11-22 22:05:45 UTC 
I couldn't build from trunk, but Will Stephenson managed to build it and transfer a file. I guess it's ok...