| Fedora This forum is for the discussion of the Fedora Project. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
10-07-2008, 11:05 AM
|
#1
|
|
Senior Member
Registered: May 2004
Location: Indianapolis, Indiana
Distribution: FC-KDE, 32 and 64 bit
Posts: 1,375
Rep:
|
FC10, No Bluetooth Mouse
FC10, eeePC 702 .
Can't get Logitech Bluetooth mouse to work .
I ran the Bluetooth Wizard and mouse is detected, but in the section
Device Setup I get the error message "Pairing with (null) failed"
In /var/log/messages
Bluetoothd[2064]: Unable to start periodic inquiry: Connection timed out (110)
This Logitech mouse worked perfect in FC9.
|
|
|
|
10-07-2008, 11:24 AM
|
#2
|
|
Member
Registered: Mar 2008
Location: Florida
Distribution: Fedora mainly, but I am open to others.
Posts: 273
Rep:
|
Fedora 10 is still in it's beta stage... not due for a final release until November. All of the kinks should be worked out by then. Report it to the development team.
|
|
|
|
10-07-2008, 12:18 PM
|
#3
|
|
Senior Member
Registered: May 2004
Location: Indianapolis, Indiana
Distribution: FC-KDE, 32 and 64 bit
Posts: 1,375
Original Poster
Rep:
|
There are no Bugs in FC10 for Bluetooth, I have had three other users say their Bluetooth Mouse was working without any problems.
So I'm having problems on my box, so that is why I'm asking for help to fix problem.
|
|
|
|
10-07-2008, 01:23 PM
|
#4
|
|
Senior Member
Registered: May 2004
Location: Indianapolis, Indiana
Distribution: FC-KDE, 32 and 64 bit
Posts: 1,375
Original Poster
Rep:
|
This is /var/log/message
Oct 7 13:01:13 eeePC bluetoothd[2048]: Bluetooth daemon
Oct 7 13:01:13 eeePC bluetoothd[2048]: Starting SDP server
Oct 7 13:01:14 eeePC bluetoothd[2048]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Oct 7 13:01:14 eeePC bluetoothd[2048]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 7 13:01:14 eeePC bluetoothd[2048]: Parsing /etc/bluetooth/network.conf failed: No such file or directory
Oct 7 13:01:14 eeePC bluetoothd[2048]: bridge pan0 created
Oct 7 13:01:14 eeePC bluetoothd[2048]: HCI dev 0 registered
Oct 7 13:01:15 eeePC bluetoothd[2048]: HCI dev 0 up
Oct 7 13:01:20 eeePC bluetoothd[2048]: Can't write class of device: Connection timed out (110)
Oct 7 13:01:25 eeePC bluetoothd[2048]: Can't write class of device: Connection timed out (110)
Oct 7 13:01:30 eeePC bluetoothd[2048]: Can't write class of device: Connection timed out (110)
Oct 7 13:01:35 eeePC bluetoothd[2048]: Can't write class of device: Connection timed out (110)
Oct 7 13:01:40 eeePC bluetoothd[2048]: Can't write class of device: Connection timed out (110)
Oct 7 13:01:40 eeePC bluetoothd[2048]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Oct 7 13:01:45 eeePC bluetoothd[2048]: Can't write class of device: Connection timed out (110)
Oct 7 13:01:45 eeePC bluetoothd[2048]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Oct 7 13:01:50 eeePC bluetoothd[2048]: Can't write class of device: Connection timed out (110)
Oct 7 13:01:50 eeePC bluetoothd[2048]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Oct 7 13:01:50 eeePC bluetoothd[2048]: Registered interface org.bluez.Service on path /org/bluez/hci0
Oct 7 13:01:50 eeePC bluetoothd[2048]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Oct 7 13:01:50 eeePC bluetoothd[2048]: Adapter /org/bluez/hci0 has been enabled
Oct 7 13:01:50 eeePC bluetoothd[2048]: Starting security manager 0
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 06:47 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|