http://bugzilla.opensuse.org/show_bug.cgi?id=904769 Roger Luedecke changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(roger.luedecke@gm | |ail.com) | --- Comment #2 from Roger Luedecke --- Created attachment 613233 --> http://bugzilla.opensuse.org/attachment.cgi?id=613233&action=edit YaST log Also noticed the log viewer in YaST says that the file is not found for any of its logs. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904769 --- Comment #4 from Josef Reidinger --- (In reply to Roger Luedecke from comment #3)

Do you need anything else from me?

no, thanks for logs. We will just need to analyse it and found why systemctl do not work. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904769 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(roger.luedecke@gm | |ail.com) --- Comment #6 from Stefan Seyfried --- bluetoothd gets started through dbus activation, maybe it did not get removed correctly? please provide the output of systemctl status bluetooth.service ls -l /etc/systemd/system/dbus-org.bluez.service ls -l /etc/systemd/system/bluetooth.target.wants/bluetooth.service Basically both files should *not* be present. Then, please do (as root): systemctl enable blueotooth.service systemctl disable bluetooth.service and paste the complete output of these two commands. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904769 --- Comment #8 from Stefan Seyfried --- So it is actually not running. How did you get to the conclusion that "After reboot, Bluetooth was still on."? In theory, even if bluetooth.service is disabled, it could be enabled via dbus-activation, but that would need /etc/systemd/system/dbus-org.bluez.service if I understand the whole thing correctly (which I'm certainly not sure about ;) Maybe it really is just the bluetooth icon in GNOME which is on? (that would be a GNOME bug) "hciconfig -a" should show something like this if a bluetooth device is present, but not active: hci0: Type: BR/EDR Bus: USB BD Address: 0C:60:76:88:2C:4C ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:1840 acl:0 sco:0 events:79 errors:0 TX bytes:1534 acl:0 sco:0 commands:79 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT or just nothing if no device is present. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904769 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #10 from Stefan Seyfried --- Ok, I'd suggest to open a new bug against GNOME (because redirecting this one again from YaST2 => bluez => GNOME does not help making the issue more clear to the developer who has to dig through the old comments :-) Of course you can reference this bug in the new report, in case the GNOME developers want to send you back to me :-P I will close this one as "invalid" as it is neither a bug in YaST2 nor in bluez. If you feel insulted by this resolution, I could also go with "worksforme" which sounds nicer, but is actually wrong (since "worksforme" is for "ok, you see strange things but nobody can reproduce them" in my opinion). Best regards and thanks for testing and reporting. Stefan -- You are receiving this mail because: You are on the CC list for the bug.