Bug 283029

Summary:	Bluetooth crash, trying to connect an Apple Aluminum Keyboard
Product:	[Unmaintained] solid	Reporter:	Vasilis.Vlachoudis
Component:	bluetooth	Assignee:	Alex Fiestas <afiestas>
Status:	RESOLVED FIXED
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Vasilis.Vlachoudis 2011-09-29 12:11:54 UTC

Application: bluedevil-input (0.1)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.4
Operating System: Linux 2.6.40.4-5.fc15.x86_64 x86_64
Distribution: "Fedora release 15 (Lovelock)"

-- Information about the crash:
I am trying to connect an Mac Aluminum BT keyboard but I cannot succeed from KDE.
I am connecting it manually with hidd --connect AA:BB:CC:DD:EE:FF, later when the keyboard goes to sleep, when I try to reconnect it pops up a dialog with options "Trust it", "Block", whatever I do it doesn't do anything and then it crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Bluetooth Input Helper (bluedevil-input), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  BlueDevil::Adapter::deviceForAddress (this=0x0, address=...) at /usr/src/debug/libbluedevil-v1.9/bluedevil/bluedeviladapter.cpp:312
#7  0x000000000040416b in InputHelper::InputHelper (this=0xe313f0, address=...) at /usr/src/debug/bluedevil-1.1.1/src/actionplugins/input/helper/inputhelper.cpp:40
#8  0x0000000000403aee in main (argc=1, argv=0x7fff024310e8) at /usr/src/debug/bluedevil-1.1.1/src/actionplugins/input/helper/main.cpp:49

Possible duplicates by query: bug 277858.

Reported using DrKonqi

Comment 1 Dario Andres 2011-09-29 12:22:15 UTC

[Comment from a bug report cleaner]
According to bug 277858 this should be fixed right now, but I don't see the version it is fixed in to check.
Regards

Comment 2 Alex Fiestas 2011-10-07 19:35:50 UTC

As Dario pointed, this is already fixed.

If you are still able to reproduce it, please don't hesitate to reopen the bug.