Bug 240314 - Bluetooth Crash conecting to Motorola Milestone
Summary: Bluetooth Crash conecting to Motorola Milestone
Status: RESOLVED DUPLICATE of bug 237877
Alias: None
Product: kbluetooth
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-01 03:06 UTC by Lorne Dmitruk
Modified: 2010-06-01 15:41 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 Lorne Dmitruk 2010-06-01 03:06:50 UTC
Application: kbluetooth (0.4)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.32.9-70.fc12.x86_64 x86_64
Distribution: "Fedora release 12 (Constantine)"

-- Information about the crash:
Was trying to coneect and pair a Motorola Milestone using Bluetooth

 -- Backtrace:
Application: KBluetooth (kbluetooth), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#5  d_func (this=0x0, mode=AutoDetect, method=..., args=...) at qdbusabstractinterface.h:154
#6  QDBusAbstractInterface::callWithArgumentList (this=0x0, mode=AutoDetect, method=..., args=...) at qdbusabstractinterface.cpp:402
#7  0x000000324d432d4b in QDBusAbstractInterface::call (this=<value optimized out>, mode=<value optimized out>, method=<value optimized out>, arg1=..., arg2=<value optimized out>, arg3=..., arg4=
    ..., arg5=..., arg6=..., arg7=..., arg8=...) at qdbusabstractinterface.cpp:694
#8  0x000000324d432f41 in QDBusAbstractInterface::call (this=<value optimized out>, method=..., arg1=..., arg2=..., arg3=..., arg4=..., arg5=..., arg6=..., arg7=..., arg8=...)
    at qdbusabstractinterface.cpp:637
#9  0x00000000004221b2 in _start ()

Possible duplicates by query: bug 238938, bug 238936, bug 237895, bug 237877, bug 237778.

Reported using DrKonqi
Comment 1 Nicolas L. 2010-06-01 15:41:58 UTC

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