FedoraThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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)
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.
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.
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.