** Changed in: bluez
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603715
Title:
bluetooth unavailable after rfkill hard (or soft) unblocking and after
suspend/re
Yes, we released pulseaudio 1:8.0-0ubuntu3.3 last week. But in testing
that I too started to suspect that the v4.8 kernel (introduced in
16.04.2?) was helping to further reduce bluetooth bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Looks as if one of these updates improved it for S2RAM, but not for
hardware switch (I mean a real physical switch in my laptop for all
wireless hardware)
libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603715
Title:
bluetooth unavailable after rfkill hard (or soft) unblocking and after
s
I'm experiencing a similar issue on Thinkpad x220 running Linux Mint 18
(based on Ubuntu 16.04) with kernel 4.4.0-21. In my case, rfkill
unblock needs to be called twice in order to fully enable (and soft
unblock) bluetooth:
# rfkill block bluetooth
# rfkill list bluetooth
0: tpacpi_bluetooth_sw:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603715
Title:
blue
** Package changed: systemd (Ubuntu) => bluez (Ubuntu)
** Project changed: systemd => bluez
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603715
Title:
bluetooth unavailable after rfkill hard (or
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603715
Title:
bluetooth unavailable after rfkill hard (or soft) unblocking and after
suspend/res
Plus, is bluetooth not operational after suspend/resume, while blocks
are not set:
rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
13: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Again, a "sudo service bluetooth restart" h
For the unreleased soft blocking, I can work around with a second
rfkill unblock bluetooth
Executing this twice makes applet-indicator black again and bluetooth is
operational (without "sudo service bluetooth restart" after a soft
unblock).
To sum it up: There's three cases:
- hard unblock with
About every second time, I get a
rfkill unblock bluetooth
thomas@lat61:~$ rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
11: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
which is what debian bug 812150 is about.
Note tha
11 matches
Mail list logo
