Bug 327132 - bluezdevil crashes during pairing with bluetooth audio device
Summary: bluezdevil crashes during pairing with bluetooth audio device
Status: RESOLVED DUPLICATE of bug 325364
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: bluetooth (show other bugs)
Version: 2.0.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-11-04 14:31 UTC by Jozef Mlich
Modified: 2013-11-04 15:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jozef Mlich 2013-11-04 14:31:54 UTC 
Application: bluedevil-audio (2.0.0)
KDE Platform Version: 4.11.2
Qt Version: 4.8.5
Operating System: Linux 3.11.6-300.fc20.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I am using fedora 20 alpha with mate. The fedora 20 is using bluez 5, however mate is not supporting that. It is suggested to use bluetooth applet from other environments.

The crash can be reproduced every time.

-- Backtrace:
Application: Bluetooth Audio Helper (bluedevil-audio), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  BlueDevil::Device::isPaired (this=this@entry=0x0) at /usr/src/debug/libbluedevil-2.0/bluedevil/bluedevildevice.cpp:203
#7  0x0000000000402e0e in AudioHelper::AudioHelper (this=0xd2f880, address=...) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/audio/helper/audiohelper.cpp:41
#8  0x0000000000402aa1 in main (argc=2, argv=0x7fff6603f3d8) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/audio/helper/main.cpp:49

The reporter indicates this bug may be a duplicate of or related to bug 325364.

Possible duplicates by query: bug 327072, bug 326110, bug 325943, bug 325364.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-11-04 15:31:41 UTC 

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