Bug 191608

Summary: A Fatal Error Occurred with Kbluetooth
Product: [Unmaintained] kde-bluetooth Reporter: Mohammad Alhobayyeb <mih1406>
Component: generalAssignee: Tom Patzig <tom>
Status: RESOLVED FIXED    
Severity: crash CC: afiestas, agchs137, andresbajotierra
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mohammad Alhobayyeb 2009-05-04 20:06:29 UTC 
Version:           KBluetooth4 Version 0.3 Using KDE 4.2.2 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

In my ASUS F8Vr with Kubuntu installed if I pushed the bluetooth button to disable it I received this message:

The application KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4) crashed and caused the signal 11 (SIGSEGV).

And if I clicked "Show Details" I receive this message:
Unable to create a valid backtrace.

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
Comment 1 Pino Toscano 2009-05-04 22:22:55 UTC 
Hello,

could you provide a backtrace for the crash? You can find more information about it in the following page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 Andreas 2009-09-06 03:50:09 UTC 
I had the same error, when I tried to use my Motorola Bluetooth Adapter.

Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4-devicemanager), signal SIGSEGV
[Current thread is 0 (LWP 8197)]

Thread 2 (Thread 0xb48d2b90 (LWP 8198)):
#0  0xb80dd430 in __kernel_vsyscall ()
#1  0xb68217b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7645380 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb757396e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb640a4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb682949e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb60da700 (LWP 8197)):
[KCrash Handler]
#6  0xb7a72515 in Solid::Control::BluetoothInputDevice::connect () from /usr/lib/libsolidcontrol.so.4
#7  0x08051330 in _start ()

I hope this helped...
Comment 3 Alex Fiestas 2009-09-23 20:07:44 UTC 
Hi, those crashes should be fixed in the 0.4 version, can you test it?

Thanks!
Comment 4 Alex Fiestas 2009-11-04 17:27:13 UTC 
Well, the off/on bugs has been fixed in 0.4 version, so this one should fixed be too.

I'm going to set this as Resolved and if you're able to reproduce it again just open it.
Comment 5 Andreas 2009-11-05 03:39:59 UTC 
Hey Alex,

Thanks for your email. Soorry, I just saw your other emails in my junk 
folder. I have not seen this issue after I reported it, so maybe it was 
a hardware issue too. I'm using an old Armada 1700, running Kubuntu 
alternate version.
Again, thank you.

Andreas

Alex Fiestas wrote:
> https://bugs.kde.org/show_bug.cgi?id=191608
>
>
> Alex Fiestas <alex@eyeos.org> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEEDSINFO                   |RESOLVED
>
>
>
>
> --- Comment #4 from Alex Fiestas <alex eyeos org>  2009-11-04 17:27:13 ---
> Well, the off/on bugs has been fixed in 0.4 version, so this one should fixed
> be too.
>
> I'm going to set this as Resolved and if you're able to reproduce it again just
> open it.
>
>
Comment 6 Alex Fiestas 2009-11-05 04:06:58 UTC 
Np, this is why I add a new comment :p

So, is this bug reproducible using 0.4 version?

Thanks!