Bug 216768 - bluetooth app crashed when i disconnected my phone's bluetooth connection
Summary: bluetooth app crashed when i disconnected my phone's bluetooth connection
Status: RESOLVED DUPLICATE of bug 212607
Alias: None
Product: kbluetooth
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-30 07:42 UTC by indigene
Modified: 2009-12-05 03:34 UTC (History)
2 users (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 indigene 2009-11-30 07:42:26 UTC
Application that crashed: kbluetooth
Version of the application: 0.4
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-15-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
i first disconnected my phone bluetooth
then went to quit the app
after quit it gave me a crash warning

 -- Backtrace:
Application: KBluetooth (kbluetooth), signal: Segmentation fault
[KCrash Handler]
#6  0x00000000 in ?? ()
#7  0x0013252f in ~BluetoothManager (this=0x8de7b08, __in_chrg=<value optimized out>) at ../../../../libs/solid/control/bluetoothmanager.cpp:100
#8  0x0013264a in ~SingletonHelper () at ../../../../libs/solid/control/ifaces/../singletondefs.h:35
#9  destroy () at ../../../../libs/solid/control/bluetoothmanager.cpp:78
#10 0x0012390b in ~KCleanUpGlobalStatic (this=0x13f3a4, __in_chrg=<value optimized out>) at /usr/include/kglobal.h:62
#11 0x053d405f in ?? () from /lib/tls/i686/cmov/libc.so.6
#12 0x053d40cf in exit () from /lib/tls/i686/cmov/libc.so.6
#13 0x053bbb5e in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#14 0x08051d31 in _start ()

Reported using DrKonqi
Comment 1 Nicolas L. 2009-11-30 16:30:22 UTC
can you install KBluetooth debug package and give again the crash log please ?
Comment 2 Dario Andres 2009-12-05 03:34:57 UTC

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