[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2017-11-17 Thread Bug Watch Updater
** 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

[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2017-07-02 Thread Daniel van Vugt
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

[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2017-06-30 Thread Thomas Mayer
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

[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2016-12-21 Thread Alberto Salvia Novella
** 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

[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2016-11-25 Thread Eric Ding
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:

[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2016-11-25 Thread Launchpad Bug Tracker
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:

[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2016-07-17 Thread Martin Pitt
** 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

[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2016-07-16 Thread Bug Watch Updater
** 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