Bug 194441

Summary: Kbluetooth crash with my mouse / keyboard logitech MX5500.
Product: kde-bluetooth Reporter: islyne
Component: kbluetoothdAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description islyne 2009-05-28 15:55:08 UTC
Version:           4 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

The bluetooth receiver for my mouse / keyboard logitech MX5500 isn't detected by Kbluetooth at startup .

 At startup, the mouse / keyboard is not detected, but if I remove the key, Kbluetooth 4 crash, and when I reconnect, the mouse is detected.

Gestionnaire de panne de KDE:

Une erreur fatale s'est produite
The application KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4) crashed and caused the signal 11 (SIGSEGV).
Cette pile des appels apparaît être inutilisable.
C'est probablement dû au fait que votre paquetage a été construit d'une manière qui empêche de créer des piles d'appels corrects, ou que le cadre de pile a été sérieusement corrompu dans l'incident.

Manager failure KDE:

A fatal error occurred
The application KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4) crashed and caused the signal 11 (SIGSEGV).
The call stack appears to be unusable.
This is probably because your package has been constructed in a manner that prevents the creation of stacks of correct calls, or the stack frame was seriously corrupted in the incident.
(traduction by google)


My pc is a toshiba 300.
Comment 1 Dario Andres 2009-09-27 14:32:05 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks
Comment 2 Andrew Crouthamel 2018-09-04 18:11:01 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.