Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#64682 - [g15daemon] systemd service wont load

Attached to Project: Community Packages
Opened by David (Marzal) - Friday, 29 November 2019, 16:21 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 24 August 2022, 06:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Evgeniy Alexeev (arcan1s)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
g15daemon systemd service fail to load because the usb keyboard is not yet recognized.
This happen every time I start/restart my computer, so the daemon is never loaded.

Additional info:
* package version: 1.9.5.3-8
* Ubuntu 18.04 has this udev rule file /lib/udev/rules.d/60-g15daemon.rules

Log:
nov 25 22:05:10 gallego systemd[1]: Starting Logitech G15 Support Daemon...
nov 25 22:05:10 gallego g15daemon[411]: Unable to attach to the G15 Keyboard... exiting
nov 25 22:05:10 gallego systemd[1]: g15daemon.service: Control process exited, code=exited, status=1/FAILURE
nov 25 22:05:10 gallego systemd[1]: g15daemon.service: Failed with result 'exit-code'.
nov 25 22:05:10 gallego systemd[1]: Failed to start Logitech G15 Support Daemon.


Steps to reproduce:
systemctl enable g15daemon
reboot
systemct status g15daemon

Workaround:
I've tried two solutions that can be mixed together, a udev rule or an improved service file.

First : a 60-g15daemon.rules compatible with systemd -> this load the service when the keyboard is recognized
Second : changed g15daemon.service file to retry 3 times with some delay before stop trying to load de daemon.

Both solutions work, alone and together.

I think that adding the udev rule and changing the service file could coexist, but one of them is at least needed in order to have a working daemon after booting the computer.
   60-g15daemon.rules (0.9 KiB)
   g15daemon.service (0.3 KiB)
   60-g15daemon_ubuntu.rules (0.8 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 24 August 2022, 06:02 GMT
Reason for closing:  None
Additional comments about closing:  pkg was dropped to AUR 2021-01-07
Comment by Adomas Jackevičius (adomas) - Sunday, 03 January 2021, 18:34 GMT
I think I have similar issue. In my case g15daemon does not fail, it does start, but it delays system start by almost 1,5min:

saus. 03 20:21:22 genesis systemd[1]: Starting Logitech G15 Support Daemon...
saus. 03 20:22:47 genesis systemd[1]: Started Logitech G15 Support Daemon.
saus. 03 20:22:48 genesis g15daemon[1020]: Booting plugin "Linux UINPUT Keyboard Output"
saus. 03 20:22:48 genesis g15daemon[1020]: Plugin "Linux UINPUT Keyboard Output" boot successful.
saus. 03 20:22:48 genesis g15daemon[1020]: Booting plugin "Clock"
saus. 03 20:22:48 genesis g15daemon[1020]: Plugin "Clock" boot successful.
saus. 03 20:22:48 genesis g15daemon[1020]: Booting plugin "LCDServer"
saus. 03 20:22:48 genesis g15daemon[1020]: Plugin "LCDServer" boot successful.

Note the timestamps between "Starting" and "Started".

Not sure how to fix this. Could you please help me?

Loading...