AstroSnail / apexctl

(Apache-2.0) Control SteelSeries Apex keyboards on GNU/Linux!
Apache License 2.0
28 stars 3 forks source link

sustemd-udevd error #12

Open Stibax opened 3 years ago

Stibax commented 3 years ago

Hi, fist i would like to thank you for this great program, for me is a must have. I'm running manjaro, and i have notice, specialy after suspend, that my usb device won't be recognized. I have analyze the system log and i found some udev continuos error about apexctl. I don't know if this error is the cause of the above problem. And i notice this behavior in the last weeks, maybe some major update have change something. But anyway if i install apexctl i have many error that you can see in the log that i have attached. If you can take a look i will apreciate. thanks apexctl.log

AstroSnail commented 3 years ago

Hi, thanks!

I looked through apexctl.log, and I'm pretty confused. It seems like udev is having trouble with the keyboard? One of the errors seems to come from here, which I think has nothing to do with apexctl.

Does the keyboard work at all? Does it work after you uninstall apexctl?

Stibax commented 3 years ago

hi, thanks for your replay. Yes the keyboard works without apexctl, and works with all the macros key with apexctl, but with this command "journalctl -b | grep udev" i see many error like this "Process '/usr/local/sbin/apexctl keys on' failed with exit code 1.". when uninstall apexctl they disappeared, but the keyboard work with apexctl (with all macros keys) and without. But i suspect that those continuos error, but i'm not sure, make the system unstable and after suspend or minutes after boot, makes usb device (exsternal hd) not to be recognized. But i understand that it's very difficult to debug, cause i'm not a linux expert and my english it's not the best. Have a nice day.

cyberlink1 commented 2 years ago

I just ran into this same issue on Fedora Core 35

Feb 20 20:02:16 *** systemd-udevd[97239]: hiddev0: Process '/usr/local/sbin/apexctl keys on' failed with exit code 1.

Any idea what is causing this? I know it is being called in the udev rules.d file for the apex keyboard. I removed the file for now.