-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aurora stops working after sleep and auto log-in #1301
Comments
Came here to post just this; +1. |
Same issue here, version 0.6.3, however my setup requires typing a password after sleep. |
Having this as well, 0.6.3 |
Same issue. #1028 <-- This is back, but with a vengeance. I have to kill Aurora every time I put the PC to sleep, or it's dead upon wakeup. |
Of note: one of the alpha releases one of the devs suggested fixes this. I’ll try and find that and link it back-I thought it was a general announcement at the time. Update: I think 0.6.3 fixed this... but others say it isn't. I haven't had the issue since I commented on this earlier in October. Maybe I have a different alpha build. I swear I got a message about this, but I can't seem to find any record of anything. I every now and then have to use the device mgr in Aurora to restart the Logitech devices, but it works consistently after being woken from sleep and when inputting passwords. Maybe it's just fixed for Logitech devices, I'm not sure. Adding your specific devices might help @antonpup and @simon-wh figure out exactly what's wonky. |
I also have this issue. Been killing and re-opening Aurora every time I wake the pc up. I am using 0.6.3 with a Corsair Strafe RGB keyboard and a Logitech G502 mouse. |
i do not get this issue anymore, nothing changed in my setup, just the issue stopped happening after some reboot. |
I still have this problem as of 1/13/19. I tried with 0.6.2b with the initial fix and it worked for a day or so but as of right now after 2 reboots I have to kill Aurora and start it up again. This is with my Logitech G810. |
Could everyone who's experiencing this issue on v0.6.3 post their log file please? Also, it may help if you disable all the devices you don't have in Device Manager |
2019-01-19 17.24.57.log |
Happens to me every day. My computer doesnt go to sleep. Leaving it on over the night i have to kill aurora when i come back to it. The keyboard lights looks ok, but the animations doesnt work. When i try to open aurora from the notification field down by the clock, nothing happens. |
Hey, could anyone experiencing this issue try this build from the above commit. I've tested waking from sleep with & without auto-login and using Corsair, Cooler Master and Wooting. Works perfectly for Corsair and Wooting, but my CM MK750 didn't want to play nice with the sdk after waking up each time, so with CM ymmv. |
Seems to be working better now. Normally would need to kill it when I get on the computer in the morning, but working fine now. Thanks! |
@noodlon Awesome! I'm going to leave this issue open for a bit to get more feedback, hopefully it's finally sorted! |
This version has been working flawlessly so far with my Logitech G512. |
works fine for me as well. |
Late to the party @simon-wh but it's working fine and stable with Logitech's G810. Thanks for the work! |
Expected behavior:
Aurora should resume upon Windows resuming from sleep
Actual behavior:
Aurora stops working after waking the machine up from sleep with the (Accounts > Sign-in options > Require sign-in set to "Never"). Under the "Device Manager" tab in Aurora all devices are stopped, pressing "start" on the desired devices (only logitech using LGS for me) does resume all functions again, as does a restart of Aurora. Basically what happened here, but while logging in normally works, auto-login doesn't. #1028 (comment)
How often does this problem occur?
This problem occurs every time the computer is waken from sleep.
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:
What is the version of Aurora you are experiencing this issue with?
My version is 0.6.3
Does the previous version of Aurora have this issue?
Yes, tried with 0.6.2b with the initial fix.
Please include any logs, screenshots, or files that are related to this issue:
The text was updated successfully, but these errors were encountered: