Closed Spolonus282 closed 1 year ago
Did you use the installer.sh to update the driver?
Can you try to start it as a service sudo systemctl start g910-gkeys
?
Yes, I did use installer.sh to update after manually uninstalling and pulling per the upgrade wiki page. After running the above command I got the same error as before.
You normally don't have to run g910-gkeys
as you described, since it is designed to run as a service.
Can you please do the following:
sudo systemctl stop g910-gkeys
/var/log/g910-gkeys.log
sudo systemctl start g910-gkeys
Now the driver should be working. Try to hit macro key G1 Take a look at the log file if it is still not working and post the content here.
If you still got the same error i assume the installation went wrong and you maybe have to try the manual installation with sudo python3 setup.py install
to see if there is any errors. You will find more information about manual install here.
I stopped the service, deleted the log, started the service and it still didn't work
I uninstalled it using sudo ./uninstall.sh
then reinstalled using the above command. After re-enabling the service and starting it, the same error occurred.
Sorry, I didn't see the request to see the log file. After deleting it as you requested, no new log file has been generated. I suspect the service is closing immediately, before it has a chance to run anything.
I have solved the issue. It seems that the old 0.2.4 package folder was not removed on uninstall for some reason. All files were removed, leaving only empty directories, meaning pip couldn't identify it and allow me to uninstall it. However, the main service module still considered it the default location (?) to check for the files, of which there were none, causing the above error. Removing the directory from dist-packages and starting the service got it to work again. I appreciate the help and am closing the issue.
Describe the bug Upon starting the service, either through computer startup or manually, nothing occurs. The logs state that a StopIteration occurred.
To Reproduce Steps to reproduce the behavior:
Expected behavior The service should start without errors
Screenshots
Additional info
Desktop:
Additional context The problem occurred directly after updating from 0.2.4 to 0.2.5. Version 0.2.4 was working fine.