Bug 475989 - latest bluetoth services seem to not work
Summary: latest bluetoth services seem to not work
Status: CLOSED DUPLICATE of bug 475069
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez-gnome
Version: 10
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-12-11 13:37 UTC by Peter Janakiev
Modified: 2008-12-11 14:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-12-11 14:30:56 UTC

Attachments (Terms of Use)

Description Peter Janakiev 2008-12-11 13:37:42 UTC
Description of problem:
I have upgraded the system on 8 of December with the following related packages (part of the upgrade all process)
After the upgrade when I select to connect the phone to the laptop (thinkpad X61s) no devices are found (i.e. device search fails).
I am sure it is not a hardware issue, because for testing purpose I booted into F10-live usb (the official release) and it worked great, the nokia is found immediately. I don't know which component exactly is broken, because I am not sure how this whole bluetooth thing works, so I cannot provide more details than this, if more is needed, please include directions on how to get debugging output. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Click on the bluetooth icon on the tray 
2. Select set up new device
3. Press forward button 
Actual results:
No device list is presented

Expected results:
List of devices by their name (as it used to do before the upgrade of the above denoted packages ) 

Additional info:
The is no issue with the bluetooth device on the laptop (it works with the live image) not the phone - without changing anything on it it works on live image F10 release and does not on the new version of the packages)

Comment 1 Bastien Nocera 2008-12-11 14:30:56 UTC

*** This bug has been marked as a duplicate of bug 475069 ***

Note You need to log in before you can comment on or make changes to this bug.