I've subscribed you to this bug because of 1) I've noticed you reported another bug, which had a fix submitted to xenial-proposed a few days ago, and I'm looking for some guidance here on how to have this bug fixed ASAP (even by me, if it means creating and submitting a new package myself or something like that, as per Ubuntu's documentation on fixing bugs) and 2) You're probably affected by it, if you own a QCA6174 and you're using a kernel later than 4.12.
I'd consider this bug a high priority one because it directly affects users (and in a very significant way), it's been already fixed in upstream since October 2017 and porting the fix to Ubuntu would be trivial, I guess.
Hi there, AceLan,
I've subscribed you to this bug because of 1) I've noticed you reported another bug, which had a fix submitted to xenial-proposed a few days ago, and I'm looking for some guidance here on how to have this bug fixed ASAP (even by me, if it means creating and submitting a new package myself or something like that, as per Ubuntu's documentation on fixing bugs) and 2) You're probably affected by it, if you own a QCA6174 and you're using a kernel later than 4.12.
I'd consider this bug a high priority one because it directly affects users (and in a very significant way), it's been already fixed in upstream since October 2017 and porting the fix to Ubuntu would be trivial, I guess.