-
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 freezes upon resuming from sleep/hibernation. Have to kill process and restart it. #1028
Comments
bump |
I'm not sure how on the radar this is, but I experience similar symptoms when I return from sleep/hibernation. |
I'm unable to replicate this using my VM (but obviously it's not an exact scenario replication). I'll try again once I get windows installed properly. Do you want to try the latest build, the issue might not be still present |
Can confirm that I hit this regularly. If the screen shuts off for a while things are okay, but if my computer hibernates then I'm forced to exit and relaunch aurora |
I've tested again on my laptop(which is a normal setup) with my Wooting One and still can't replicate the issue, I can sleep and hibernate and when it returns it works fine. |
Has anyone still experienced this issue on v0.6.2b? |
Haven't noticed it since the update, but also been more keen on shutting off my computer when I'm not using it. I'll test this when I get home (a few days) |
@husseinfahmy Okay, cool, thanks for getting back to me! |
I have this problem since I changed from a G900 to G903 with Powerplay. I have to unplug the Powerplay mat (wich doubles as the mouse receiver) upon resume from sleep to be able to run Aurora again. |
@gradius-v Do you have a log file for when that happened? |
Yes, but it shows no errors. Aurora also doesn't crash, it makes LGS hang. Unplugging the Powerplay mat & restarting Aurora immediately restores funtionality. |
@gradius-v you might be able to avoid restarting aurora by going into settings -> Device manager and stopping and starting the Logitech device Also, I think the solution might be to turn off all the device integrations when sleep mode is detected and reconnecting when restored. |
@gradius-v Actually, could you try this build, I've implemented what I mentioned above but I cannot test it properly in the vm I'm using. |
Just tried it. G903/Powerplay lighting survives resume from sleep, but now I have to wait ~10sec at the login screen before the keyboard lets me type my password. Maybe make it configurable wich devices to disconnect before sleep? |
@gradius-v The hook that I used for tracking sleeping/resuming seems to trigger when the lockscreen appears, I can see about getting it to trigger after unlocking if you run into the issue again |
@mmmboost @ChickenJoe124 @KairuByte Could you try the build I linked above and see if it solves it for you as well? |
@simon-wh don't see this anymore |
Going to close this issue for now, if anyone runs into this issue again let me know! |
I came back for me. If I let the PC sleep several hours and LGS is dead every single time i resume. |
|
@gradius-v Once this build for the above commit is done could you try it out? I changed it so it shouldn't have a scenario where devices are reinitialized between being shutdown for going to sleep and actually going to sleep. I also made it only reconnect after you login, which should hopefully fix some of your issues. |
Thanks, I will test the new build as soon as I'm home. |
Works as it should ! LGS now survives a long sleep. |
@gradius-v Awesome! Thanks for getting back to me! |
@simon-wh hey, so I'm on 0.6.3 and I'm having this issue when I set windows to auto log in (sign in options > never require password). I think bypassing the lock screen also bypasses the trigger you implemented to start the device again. Thank you! |
@yiweitech So it turns off but doesn't turn on again when you wake up? Could you make a new issue for it? |
@simon-wh still happens for me for I have a Wooting II / Logitech G502. When resuming, devices have ther "original" lighting effects. Then, "after some time", Aurora adds one snapshot of the activated profile ( Aurora CPU usage is 2%~4%, the tray-right-click menu freezes forever open, and window (if I manage to open it) stays white forever and it is almost un-responsive (however, it responds with a huge delay to e.g. It seems that some kind of memory leak is going on (I was waiting for your response before I killed it; now the process has It seems that, deterministically, Aurora cannot handle Sleep/Hibernate. Resuming today, it seems working; however, |
I also see a similar issue with a Razer keyboard. Often when waking from sleep, it'll take on the effect from Synapse, but kind of glitchy since some of the Aurora lighting seems to show through. Either restarting Aurora or turning Chroma Connect off and on again from Synapse fixes the problem. |
After updating to GHUB because of a new G903 Hero this is back. Aurora is completely dead after sleep/resume.. |
@simon-wh Still an issues now, have to kill the process and restart aurora to get my keyboard to light up. Keyboard is drevo blademaster pro. Not sure where the log file lives, can't see it in app directory. |
What are you experiencing an issue with?
What kind of an issue is it?
Expected behavior:
Aurora works great if i start the program and adjust settings/profiles/etc. It even senses game profiles more accurately than my SteelSteries mouse software. The problem comes in when waking my computer up from sleep/hibernate. None of the lighting profiles or changes seem to register.
Actual behavior:
After waking my PC up, nothing from Aurora seems to register with my keyboard. The profile is not restored and making any changes in the aurora software does nothing. It seems like the computer sleeping has broken the link between the program and the keyboard. In order to get keyboard lighting working again, I have to go into the task manager, kill the process, and then run it again in administrator mode. I believe the same thing happens when I restart my computer as well, but I would have to do some testing.
How often does this problem occur?
Every time I wake my computer from sleep/hibernate.
Also happening on first startup of windows.
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:
Have Aurora running (minimized in taskbar if that matters)
Allow computer to go into sleep mode.
Wake computer from sleep mode.
Start computer.
Log into windows.
Aurora starts up on it's own and is running. Says its connected to keyboard, but no lighting profile is active.
What is the version of Aurora you are experiencing this issue with?
v0.6.1
Does the previous version of Aurora have this issue?
Not sure, this is the first version I have used.
Please include any logs, screenshots, or files that are related to this issue:
The first log is the first one after waking my PC up. It looks like it's not initializing properly. The second log is from restarting Aurora after killing the process. And just posted a new log of a fresh boot.
2018-03-17 11.20.23.log
2018-03-17 11.20.41.log
2018-03-17 12.00.08.log
The text was updated successfully, but these errors were encountered: