Bug 328992 - Bluetooth Network Helper crashes on Connect to Dail Up Network
Summary: Bluetooth Network Helper crashes on Connect to Dail Up Network
Status: RESOLVED DUPLICATE of bug 326871
Alias: None
Product: solid
Classification: Unmaintained
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-12-19 05:30 UTC by bugzy
Modified: 2013-12-19 06:44 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugzy 2013-12-19 05:30:51 UTC
Application: bluedevil-network-dun (2.0.0)
KDE Platform Version: 4.11.3
Qt Version: 4.8.5
Operating System: Linux 3.11.10-301.fc20.x86_64+debug x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
-Paired phone (n900) with laptop
-Select Bluetooth in Dolphin
-Locate device and select Dail up network
-Note problem may be related to bluetooth being handled by bluetoothctl in Fedora 20 (rather than bluetoothd as in Fedora 19, since it works as it should in Fedora 19)

The crash can be reproduced every time.

-- Backtrace:
Application: Bluetooth Network Helper (bluedevil-network-dun), 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 NetworkDUNHelper::NetworkDUNHelper (this=0xea4290, address=...) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/networkdun/helper/networkdunhelper.cpp:43
#8  0x0000000000402aa1 in main (argc=2, argv=0x7fff8b079038) at /usr/src/debug/bluedevil-2.0.0/src/actionplugins/networkdun/helper/main.cpp:49

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-12-19 06:44:21 UTC

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