-
Notifications
You must be signed in to change notification settings - Fork 15
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
Suspend/Resume issue #9
Comments
The errors looks exactly as the device got disconnected and g13d should wait around for a device to be inserted but the daemon might have gotten terminated by the system and not started on insertion. When this happens, can you see the device in the list when running |
For the first case the logs spit out a lot more in a loop before I killed it myself. I didn't capture all of it. Here is the lsusb output after I killed it.
Here is the output where I did a suspend first, then hibernate.
|
I did a suspend/resume with g13d running manually and it lost track of the gamepad. I was able to kill and restart it fine and things worked again but I am not yet sure how to configure this to be done automatically.
I don't see anything in the systemd service file that would trigger the restart but I am not sure.
This is on Debian 10/Buster.
Logs
The text was updated successfully, but these errors were encountered: