Bug 220753 - kdebluetooth crashed after transfering files from the mobile
Summary: kdebluetooth crashed after transfering files from the mobile
Status: RESOLVED FIXED
Alias: None
Product: kbluetooth
Classification: Unmaintained
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-12-31 00:56 UTC by Miguel Tadeu
Modified: 2010-01-31 21:22 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 Miguel Tadeu 2009-12-31 00:56:27 UTC
Application that crashed: kbluetooth
Version of the application: 0.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.6.0
Operating System: Linux 2.6.31-16-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Hi. After transfering the files(successfuly), the files were still in the notification area. After forcing a close at the notification area(so the file transfers would go away) kdebluetooth crashed, leaving this crash report

 -- Backtrace:
Application: KBluetooth (kbluetooth), signal: Segmentation fault
[KCrash Handler]
#6  0x002bd86c in QDBusAbstractInterfacePrivate::canMakeCalls (this=0x9fb6730) at qdbusabstractinterface.cpp:106
#7  0x002bddf8 in QDBusAbstractInterface::callWithArgumentList (this=0x9df5720, mode=QDBus::AutoDetect, method=..., args=...) at qdbusabstractinterface.cpp:404
#8  0x002c16f8 in QDBusAbstractInterface::call (this=0x9df5720, mode=QDBus::AutoDetect, method=..., arg1=..., arg2=..., arg3=..., arg4=..., arg5=..., arg6=..., arg7=..., arg8=...)
    at qdbusabstractinterface.cpp:700
#9  0x002c195c in QDBusAbstractInterface::call (this=0x9df5720, method=..., arg1=..., arg2=..., arg3=..., arg4=..., arg5=..., arg6=..., arg7=..., arg8=...) at qdbusabstractinterface.cpp:643
#10 0x08070fa9 in _start ()

Reported using DrKonqi
Comment 1 Alex Fiestas 2010-01-31 21:22:03 UTC
This bug has been fixed in the last RC, when we release 0.4 version I'll ask kubuntu developers to upgrade.

Thanks!