[Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

I just installed an newer ubuntu mainline kernel (4.13.9) and the issue is fixed as described by Kai-Heng Feng. The new problem with that now is that closing the laptop lid doesn't do anything, even though I have set the AC and battery action to 'suspend' in dconf-editor. I do hope that this is

[Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

Thank you for your swift response. That's good to hear it's not so far away. In the meantime does anyone know any workaround for restarting/shutting down a stuck system? I don't feel really comfortable holding down the power button every time and unfortunately I have to use ubuntu every day at

[Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

This also affects me. I can't shutdown my laptop unless I hold down the power button. Happens every time. Kai-Heng Feng you mention that this will be fixed in the next kernel release. Any idea roughly when that would be? I tried booting with 4.10 kernel but that didn't seem to work very well on

Re: [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

I tried connecting to 5GHz at work today and it did not work. I am using adam's copy paste suggestion from earlier posts. Nomal wifi networks work fine. On Thu, Nov 5, 2015 at 7:55 PM, Roman <1383...@bugs.launchpad.net> wrote: > I didn't used the new purposed firmware-package because i

Re: [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Has anyone done proper testing of this on 5GHz wifi networks? On Thu, Nov 5, 2015 at 1:59 PM, Seth Forshee wrote: > Adding verifycation-done tag based on positive test results in comments > #325 and #326. > > ** Tags added: verification-done > > -- > You received

[Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Hello chevrier. Sorry to hear about your problem. Even though I'm sure this isn't the answer you are looking for, could you please make sure this is not a router problem? I mean, do you have access to the internet over the same wifi connection on another device? Kind of sounds like you've

[Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Hello. If the wifi isnt working with what you have there right now, yes. Replace them with the files Adam suggested. It worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title:

Re: [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

If you have no wifi with the files that are currently in there, then yes. Repalce them with the ones Adam mentioned On Mon, Oct 26, 2015 at 7:56 PM, Praveen Sundar wrote: > Hello Dimitrios, > I recently upgraded to Ubuntu Wily. I found that there's already a copy of > hw2.1

[Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Hello. I am here to first of all thanks Adam once again for his fast response and secondly to confirm that, after Adam's suggestion on the new status, my wifi is now working on Wily 15.10. All I did was copy the files from the link manually into /lib/firmware/ath10k/ Here is an output of dmesg

[Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Hello. I have been using the .deb file for a few months on 15.04 and everything was working great. I just updated to 15.10 Wily and unfortunately this broke wifi once again... I tried doing 'sudo rm -rf /lib/firmware/ath10k' and then pasting in the ath10k folder from the github repo you have

[Bug 874146] Re: Multimonitor: New windows open on the wrong monitor, Place Plugin settings silently ignored

Ubuntu 14.10 here and I am having this issue. My laptop screen (which I want to use as primary) is on the right and my external monitor (secondary) on the left. Some windows (such as Viber and the Skype Login screen and Options) open on the secondary screen for no reason. -- You received this