Bug 709103

Summary: Cannot configure bluetooth devices
Product: [Fedora] Fedora Reporter: Juan Manuel Rodriguez <nushio>
Component: bluedevilAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: jreznik, kevin, ltinkl, mgress, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:38:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Juan Manuel Rodriguez 2011-05-30 16:03:11 UTC
Description of problem:
I tried configuring a bluetooth mouse on KDE. It hangs attempting to pair the mouse. 

Version-Release number of selected component (if applicable):
[Nushio@Serenity ~]$ rpm -q bluedevil
bluedevil-1.1-2.fc15.x86_64

How reproducible:
Extremely. 

Steps to Reproduce:
1. Get a bluetooth mouse
2. Attempt to configure it
3. It hangs
  
Actual results:
Konsole says: 
Error response:  "Host is down" 

Expected results:
Bluetooth mouse actually working

Additional info:
I managed to pair the device under the Gnome bluetooth library, which bluedevil recognized. 

Bluedevil also fails to send files to my Nexus One, not sure if I should open a separate ticket for this though.

Comment 1 Jaroslav Reznik 2011-05-31 10:58:30 UTC
Hi,
I'm unable to try to reproduce as I don't have a BT mouse but I'll try to get one.

For filetransfer issue, please, open a new separate bug. But it works for me - tested with Maemo and Symbian operating systems.

Comment 2 Jaroslav Reznik 2011-05-31 11:20:55 UTC
Ok,
I have a BT mouse now, thanks psiroky. It works for me flawlessly - it was discovered, connected and I can use it - pointer moves.

Could you try to generate debug logs? Run kdebugdialog and search for "blue" substring and enable all checkboxes. Then kill bluedevil, start it in shell and please paste output. Thanks.

Comment 3 Juan Manuel Rodriguez 2011-06-01 02:46:29 UTC
Okay, I tried kdebugdialog (I'm new to KDE, glad there's a tool like this), but filtering "blue" brought nothing. I probably need to install some debug package, but yum returned nothing that seemed obvious when I searched for 'blue'

Comment 4 mark gress 2011-06-17 01:08:07 UTC
Hey JRez, I'm having an issue with bluedevil where it doesn't even recognize my bluetooth adapter.  I looked over some of your instructions in this bug report, but when I run kdebugdialog and search for "blue", no results show up.

Using a search engine, I noticed a bug report with another distro which deals with bluedevil having an issue trying to detect a bluetooth adapter; which asks for LSUSB output:

[user@localhost ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 007: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 003 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 014: ID 045e:007e Microsoft Corp. Wireless Transceiver for Bluetooth

My base USB subsystem seems to recognize the adapter, so it's bluedevil w/ the issue.(or else kernel I guess)  I figured since there was already a bug report in bugzilla regarding bluedevil that I'd just latch on, but should I file a whole new report?

Thanks.

Comment 5 mark gress 2011-07-21 19:37:47 UTC
There were recently some updates on the servers, bluez and the kernel stood out at the time.  Everything appears to be working now.  No issues with bluedevil, adapter is recognized as expected, devices connect fine.  Thanks.

Comment 6 Fedora End Of Life 2012-08-07 16:39:02 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping