Description of problem: I upgraded from Mageia 1 to Mageia two a week ago. On Mageia 1, my bluetooth mouse was working well. If I booted up, or resume, I could turn my bluetooth mouse, and it would work without any further actions. bluedevil would show my bluetooth adapter, and various actions were available. On Mageia 2, the bluedevil status bar icon states 'No bluetooth adapters found', however: [root@tiger ~]# hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:24:7E:5D:9A:80 ACL MTU: 1017:8 SCO MTU: 64:8 UP RUNNING RX bytes:119650 acl:7226 sco:0 events:212 errors:0 TX bytes:1381 acl:47 sco:0 commands:58 errors:0 After a suspend, the adapter is down, and I need to manually bring it up, and manually connect to the bluetooth mouse. Version-Release number of selected component (if applicable): bluedevil-1.3-0.rc2.1.mga2 How reproducible: Always. Steps to Reproduce: 1. Boot and log in to KDE 2. Start bluedevil from the menu 3. Right click on the bluetooth status bar icon, and see it says 'No adapters found'
Hi I have the same problem: [root@localhost gouessej]# hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:15:83:C9:32:3D ACL MTU: 310:10 SCO MTU: 64:8 DOWN RX bytes:460 acl:0 sco:0 events:17 errors:0 TX bytes:70 acl:0 sco:0 commands:16 errors:0
CC: (none) => gouessej
[root@localhost gouessej]# lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c040 Logitech, Inc. Corded Tilt-Wheel Mouse Bus 002 Device 002: ID 043d:0029 Lexmark International, Inc. Scan Print Copy Bus 002 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 004: ID 0926:2526
I did that to work around the problem: [root@localhost gouessej]# systemctl restart dbus-org.bluez.service Failed to issue method call: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. [root@localhost gouessej]# systemctl status bluetooth.service dbus-org.bluez.service bluetooth.service - Bluetooth Manager Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/bluetooth.service dbus-org.bluez.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) [root@localhost gouessej]# systemctl enable bluetooth.service ln -s '/lib/systemd/system/bluetooth.service' '/etc/systemd/system/dbus-org.bluez.service' ln -s '/lib/systemd/system/bluetooth.service' '/etc/systemd/system/bluetooth.target.wants/bluetooth.service' [root@localhost gouessej]# systemctl restart dbus-org.bluez.service
CC: (none) => peter.winterflood
Julien, you have to have your device UP
(In reply to Manuel Hiebel from comment #4) > Julien, you have to have your device UP Can you elaborate please? What should I do to permit my device to be UP?
hciconfig hci0 up
(In reply to Manuel Hiebel from comment #6) > hciconfig hci0 up Thanks. I'll install Mageia Linux 3 and I'll try your command in order to confirm that it really works as expected.
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD