Bug 147300

Summary: Adding Logitech diNovo Bluetooth Keyboard causes KDEInputWizard SIGSEGV
Product: kde-bluetooth Reporter: Selim Baygin <selimbaygin>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED FIXED    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: kinputwizard's backtrace after the SIGSEGV crash
Backtrace with debug symbols

Description Selim Baygin 2007-06-27 18:26:44 UTC 
Version:           1.0_beta3 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 4.1.2 (Gentoo 4.1.2) 
OS:                Linux

I have a new Logitech Media Desktop Laser combo with the bluetooth keyboard.  When I use the KBluetooth application to add the keyboard as an Input Device, the application crashes with a SIGSEGV signal error.
Here are the steps followed to reproduce this crash:
1. Right click on bluetooth icon on the desktop panel.
2. Select Configuration, Input Devices.
3. Press the "Connect" button on the bottom of the keyboard.
4. Press the "Ann new Device" button on the Input Devices dialog.
5. After the search completed, select the "Logitech diNovo Keyboard" item.
6. Click "Setup" (or "Connect", same result).

Results:
1. The dialog box disappears.
2. A "KInputWizard - KDE Crash Handler" dialog pops up.
3. Message reads: "The application KInputWizard (kinputwizard) crashed and caused the signal 11 (SIGSEGV).
4. Attached backtrace is generated.
Comment 1 Selim Baygin 2007-06-27 18:27:28 UTC 
Created attachment 20982 [details]
kinputwizard's backtrace after the SIGSEGV crash
Comment 2 Pino Toscano 2007-06-27 20:18:39 UTC 
That backtrace is not really useful, please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports.
Comment 3 Selim Baygin 2007-06-27 22:41:22 UTC 
Created attachment 20983 [details]
Backtrace with debug symbols
Comment 4 Daniel Gollub 2007-07-10 16:42:13 UTC 
This should be fixed in SVN already.
We plan to release kdebluetooth 1.0 beta4 in the next days.