[Bug 847860] New: BlueDevil does not find bluetooth adapted anymore
https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c0 Summary: BlueDevil does not find bluetooth adapted anymore Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: adrian@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- BlueDevil says that there are no bluetooth adapter in my hardware, that worked with 12.3. Also configuring bluetooth manual on command line leads to a working setup. BlueZ version 5 update may have caused this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c1
--- Comment #1 from Adrian Schröter
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c2
--- Comment #2 from Adrian Schröter
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c3
Adrian Schröter
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c4
Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c5
Richard Fenoglio Jr
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c6
Richard Fenoglio Jr
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c7
Richard Fenoglio Jr
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c8
Dmitry Ashkadov
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c9
--- Comment #9 from Juan Ehrenhaus
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c10
Vladimir Botka
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c11
--- Comment #11 from Adrian Schröter
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c12
Dieter Brozio
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c13
--- Comment #13 from Oliver Neal
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c14
--- Comment #14 from Vladimir Botka
I can confirm that bluetooth problems still exists in 13.1 (KDE). I can connect my Microsoft bluetooth keyboard manually with bluetoothctl, but it only reconnects after login. Is there any start-up script which could start this bluetoot before user login?
Very probably the controller is down. You can check it from the terminal 1) Ctrl-ALt-F1 2)login as root 3)hciconfig -a If so, you can bring it up #hciconfig hci0 up. There are some discussions how-to solve this systematically https://bbs.archlinux.org/viewtopic.php?id=166362 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c15
--- Comment #15 from Oliver Neal
(In reply to comment #13)
I can confirm that bluetooth problems still exists in 13.1 (KDE). I can connect my Microsoft bluetooth keyboard manually with bluetoothctl, but it only reconnects after login. Is there any start-up script which could start this bluetoot before user login?
Very probably the controller is down. You can check it from the terminal 1) Ctrl-ALt-F1 2)login as root 3)hciconfig -a
This command tells: hci1: Type: BR/EDR Bus: USB BD Address: 00:07:61:E3:72:65 ACL MTU: 1017:7 SCO MTU: 64:1 DOWN RX bytes:471 acl:0 sco:0 events:18 errors:0 TX bytes:76 acl:0 sco:0 commands:18 errors:0 Features: 0xff 0xfe 0x8d 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT hci0: Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: SLAVE ACCEPT
If so, you can bring it up #hciconfig hci0 up. There are some discussions how-to solve this systematically https://bbs.archlinux.org/viewtopic.php?id=166362
adding a /etc/udev/rules.d/10-local.rules with this content: # Set bluetooth power up ACTION=="add", KERNEL=="hci1", RUN+="dbus-send --system --type=method_call --print-reply=literal --dest=org.bluez /org/bluez/hci1 org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1 string:Powered variant:boolean:true" did not change a thing. Keyboard is avaible a few seconds after login. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c16
--- Comment #16 from Vladimir Botka
adding a /etc/udev/rules.d/10-local.rules with this content:
# Set bluetooth power up ACTION=="add", KERNEL=="hci1", RUN+="dbus-send --system --type=method_call --print-reply=literal --dest=org.bluez /org/bluez/hci1 org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1 string:Powered variant:boolean:true"
did not change a thing. Keyboard is avaible a few seconds after login.
dbus might not be available when the controler is registred. Probably plain "hciconfig hci1 up" might fit the purpose better. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c17
--- Comment #17 from Oliver Neal
dbus might not be available when the controler is registred. Probably plain "hciconfig hci1 up" might fit the purpose better.
I did try this. No change :( Did not resolve my problem. Any other hint? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c18
--- Comment #18 from Vladimir Botka
Did not resolve my problem. Any other hint?
Yes. As a hint. Wana try this one :) I've tried the systemd service below as of the comment http://archlinuxarm.org/forum/viewtopic.php?f=31&t=5935 ,but unfortunately didn't succeed. # systemctl daemon-reload # systemctl start bluetooth-up The command didn't return and journalctl says Nov 27 11:14:24 probook systemd[1]: Starting Bring Up Bluetooth... Very probably I'm missing something. # cat /usr/lib/systemd/system/bluetooth-up.service [Unit] Description=Bring Up Bluetooth After=bluetooth.target [Service] Type=oneshot ExecStart=/usr/bin/hciconfig hci0 up # TimeoutSec=0 # StandardInput=tty # RemainAfterExit=yes [Install] WantedBy=bluetooth.target -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=847860
https://bugzilla.novell.com/show_bug.cgi?id=847860#c19
--- Comment #19 from Oliver Neal
participants (1)
-
bugzilla_noreply@novell.com