Bug 246225 - Kbluetooth not working at all
Summary: Kbluetooth not working at all
Status: RESOLVED DUPLICATE of bug 214834
Alias: None
Product: kbluetooth
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.4
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-30 11:23 UTC by Kamil
Modified: 2010-08-13 20:48 UTC (History)
1 user (show)

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 Kamil 2010-07-30 11:23:21 UTC
Application: kbluetooth (0.4)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.34-12-desktop i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
While changing device visibility, kbluetooth crashing. Always.
Also on my Eee PC 1000 BT cannot discover any device. Previous version which I used (from opensuse 11.2) worked great.

 -- Backtrace:
Application: KBluetooth (kbluetooth), signal: Segmentation fault
[KCrash Handler]
#6  d_func (this=0x0, mode=QDBus::AutoDetect, method=..., args=...) at qdbusabstractinterface.h:154
#7  QDBusAbstractInterface::callWithArgumentList (this=0x0, mode=QDBus::AutoDetect, method=..., args=...) at qdbusabstractinterface.cpp:402
#8  0xb63739e1 in QDBusAbstractInterface::call (this=0x0, mode=QDBus::NoBlock, method=..., arg1=..., arg2=..., arg3=..., arg4=..., arg5=..., arg6=..., arg7=..., arg8=...)
    at qdbusabstractinterface.cpp:694
#9  0xb6373c44 in QDBusAbstractInterface::call (this=0x0, method=..., arg1=..., arg2=..., arg3=..., arg4=..., arg5=..., arg6=..., arg7=..., arg8=...) at qdbusabstractinterface.cpp:637
#10 0x0806aa12 in _start ()

This bug may be a duplicate of or related to bug 237778.

Possible duplicates by query: bug 244904, bug 244185, bug 244056, bug 242838, bug 240314.

Reported using DrKonqi
Comment 1 Nicolas L. 2010-08-13 20:48:16 UTC

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