Bug 236532 - [Lucid] kbluetooth crashes after setting device name
Summary: [Lucid] kbluetooth crashes after setting device name
Status: RESOLVED NOT A BUG
Alias: None
Product: kbluetooth
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-06 10:35 UTC by Tomasz Czapiewski
Modified: 2010-05-06 13:21 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 Tomasz Czapiewski 2010-05-06 10:35:07 UTC
Application: kbluetooth (0.4)
KDE Platform Version: 4.4.3 (KDE 4.4.3)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic x86_64
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
I've had working kbluetooth configuration a month ago on Kubuntu Lucid, after that I've installed blueman package with aulirus. After removing blueman (and rebooting the system) I've tried once more kbluetooth and it had no device name, MAC 00:00:00:00:00:00 and visibility set to invisible (I've had discoverable before). When I try to set device name and accept configuration kbluetooth crashes.
Tried on both official KDE 4.4.2 in Kubuntu Lucid and 4.4.3 from Kubuntu PPA.


The crash can be reproduced every time.

 -- Backtrace:
Application: KBluetooth (kbluetooth), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f6b9931c760 (LWP 8260))]

Thread 2 (Thread 0x7f6b8755e710 (LWP 8264)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f6b8755daa0 in ?? ()
#2  0x00007fff4ecc4852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f6b9931c760 (LWP 8260)):
[KCrash Handler]
#5  QDBusAbstractInterface::d_func (this=0x0, mode=QDBus::AutoDetect, method=..., args=...) at qdbusabstractinterface.h:154
#6  QDBusAbstractInterface::callWithArgumentList (this=0x0, mode=QDBus::AutoDetect, method=..., args=...) at qdbusabstractinterface.cpp:402
#7  0x00007f6b960dc43d in QDBusAbstractInterface::call (this=<value optimized out>, mode=<value optimized out>, method=<value optimized out>, arg1=..., arg2=..., arg3=..., arg4=..., arg5=..., 
    arg6=..., arg7=..., arg8=...) at qdbusabstractinterface.cpp:694
#8  0x00007f6b960dc6d1 in QDBusAbstractInterface::call (this=0x0, method=<value optimized out>, arg1=<value optimized out>, arg2=<value optimized out>, arg3=<value optimized out>, arg4=..., 
    arg5=..., arg6=..., arg7=..., arg8=...) at qdbusabstractinterface.cpp:637
#9  0x0000000000425422 in _start ()

Possible duplicates by query: bug 235885, bug 235188, bug 234741, bug 214834.

Reported using DrKonqi
Comment 1 Tomasz Czapiewski 2010-05-06 13:21:27 UTC
It looks like a hardware bug.
After powering off and on my laptop kbluetooth worked without problems properly saw my bluetooth device and now it doesn't crash when changing adapter settings.
I've been rebooting and powering on and off device (hardware switch) before and this didn't help, I had to shutdown system and power it on again but and problem was not only the kbluetooth - every bluetooth application had simmilar problems here.

Sorry for confusion.