[Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-02-10 Thread noob saibot
** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615774 Title: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: H

[Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-02-10 Thread noob saibot
Nope, I celebrated too early. I still get this error with the updated bios. Apparently less frequently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615774 Title: iwlwifi queue stuck, Microcode SW

[Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-02-09 Thread noob saibot
Bios update helped in my case. I had this problem every 5-15 min. First got "Queue stuck" then "Microcode SW error detected" I have the same firmware Loaded firmware version: 16.242414.0 as the OP but a slightly newer kernel: uname -r 4.4.0-59-generic I have a Lenovo Yoga 260 and Network contro

[Bug 898853] Re: Touch: Unity hijacks multitouch gestures

2016-03-11 Thread noob saibot
@bregma Is this still the state of this issue? Or did you change your opinion in the meantime? I think users are capable to decide for themselves in how far the preset gestures are a fundamental part of unity or if they would still have some use (and maybe even more) for unity after changing them.

[Bug 842693] Re: Touchpad gesture not customizable or cannot turn off all or selected gestures

2016-03-11 Thread noob saibot
I am on unity 7.4.0 which is part of the ubuntu 16.04 nightly builds at the moment. I must say that the fact that this situation has still not changed seems to show a bug in the whole development process of unity. Getting to this bug report just cost me more than 2 hours of my time looking for solu