http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c2 --- Comment #2 from Bernhard Wiedemann --- I cannot reproduce it on my Acer B-115M laptop. rfkill shows a change in 1: acer-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no and when restarting blueberry, it still shows the status as off. Maybe because you have a different kind of bluetooth adapter? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c4 --- Comment #4 from S. B. --- Created attachment 657693 --> http://bugzilla.opensuse.org/attachment.cgi?id=657693&action=edit Bluetooth "on" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c6 --- Comment #6 from S. B. --- Created attachment 657695 --> http://bugzilla.opensuse.org/attachment.cgi?id=657695&action=edit Blueberry closed -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c8 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel Assignee|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #8 from Bernhard Wiedemann --- It looks as if the soft-blocked bit is never set. Could be a kernel bug around rfkill. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c10 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com Component|Kernel |Network Assignee|kernel-maintainers@forge.pr |sor.alexei@meowr.ru |ovo.novell.com | --- Comment #10 from Takashi Iwai --- OK, then this looks more like a blueberry-specific problem. Reassigned to blueberry maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c12 --- Comment #12 from S. B. --- Hi Alexei, how can I rule out the possibility of a gnome-bluetooth bug? I have the "gnome-bluetooth" package installed, but it appears to consist of just icons and documentation files. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 Alexei Sorokin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sb56637@gmail.com Flags| |needinfo?(sb56637@gmail.com | |) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c15 --- Comment #15 from Alexei Sorokin --- S. B., and it really only happens with blueberry? That's very-very unlikely that it does. Confirming that it doesn't will allow me to reassign this bug to the GNOME maintenance team as gnome-bluetooth is their package. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c17 Maurizio Galli changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maurizio.galli@gmail.com --- Comment #17 from Maurizio Galli --- Is there any update on this? I just noticed I have the same issue. However no problems when using Blueman Device: Lenovo Thinkpad T460 DE: Xfce OS: Tumbleweed Blueberry version: 1.2.3-2.1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c19 --- Comment #19 from Maurizio Galli --- (In reply to S. B. from comment #18)

At some point during the past few months in Tumbleweed it seems to have just magically started working.

ok well I run a few more tests and if I don't get anywhere I will open a new report -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c21 --- Comment #21 from Alexei Sorokin ---

I guess it requires rfkill which was its own small package before, but now is part of util-linux so it is always there.

Bernhard, it was always taken into account. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c23 Alexei Sorokin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- Flags|needinfo?(sb56637@gmail.com |needinfo?(maurizio.galli@gm |) |ail.com) --- Comment #23 from Alexei Sorokin --- S. B., no, that is probably not it. When that button is toggled, this is exactly what happens: https://github.com/linuxmint/blueberry/blob/1.2.3/usr/lib/blueberry/rfkillMa... That is, "/usr/sbin/rfkill block bluetooth" is being executed wrapped in magic. Maurizio, can you check if the above command works on its own? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c25 --- Comment #25 from Maurizio Galli --- (In reply to Alexei Sorokin from comment #24)

Maurizio, also check please if /usr/bin/rfkill exists (it should not).

The command /usr/sbin/rfkill block bluetooth as root works and also I have rhe file /usr/sbin/rfkill -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c27 --- Comment #27 from Alexei Sorokin --- Maurizio, whether /usr/bin/rfkill exists, in /usr/bin/, not /usr/sbin/ Do I understand it right that from the user "/usr/sbin/rfkill block bluetooth" does 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=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c29 --- Comment #29 from Maurizio Galli --- (In reply to Alexei Sorokin from comment #27)

Maurizio, whether /usr/bin/rfkill exists, in /usr/bin/, not /usr/sbin/

Do I understand it right that from the user "/usr/sbin/rfkill block bluetooth" does not work?

Same as when I run the command alone, when using the switch I get the following "rfkill: cannot open /dev/rfkill: Permission denied" I posted a screenshot here: https://imgur.com/a/WUU03on -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c31 --- Comment #31 from Maurizio Galli --- (In reply to Alexei Sorokin from comment #30)

Maurizio, I think I know what's going on… Try to install gnome-settings-daemon, reboot and see if it works then.

I think existence of /usr/lib/udev/rules.d/61-gnome-settings-daemon-rfkill.rules is what does it.

I will try but I hope there is a more graceful way to achieve this... There are too many recommended Gnome dependencies pulled in by gnome-settings-daemon -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c33 --- Comment #33 from Maurizio Galli --- (In reply to Alexei Sorokin from comment #32)

Maurizio, yeah, I'm just trying to prove a theory :-).

:-) your theory was correct. The switch works now PS: I temporarily disabled "recommended packages" because I didn't wanna deal with that mess ;) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c37 --- Comment #37 from Alexei Sorokin --- Bernhard, I just mirrored the decision made in gnome-settings-daemon's upstream to get the fix as fast as possible (with the precedence). Really not sure why access to /dev/rfkill is not permitted by default to a regular user in 50-udev-default.rules. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 http://bugzilla.opensuse.org/show_bug.cgi?id=957071#c40 --- Comment #40 from Alexei Sorokin --- Maurizio, no, it can be safely removed. -- You are receiving this mail because: You are on the CC list for the bug.