Hello, at computer startup, the lircmd daemon is started automatically. But this particular daemon does not create any ".pid" file, whereas systemd looks for "/var/run/lircmd.pid" . So, systemd waits a long time for the service to start, even if the daemon is correctly started instantly, because the PID file is never created. Then it gives up and the service state is "timeout". $ systemctl status lircmd.service lircmd.service - LSB: Linux Infrared Remote Control mouse daemon Loaded: loaded (/etc/rc.d/init.d/lircmd) Active: failed (Result: timeout) since Tue, 14 Aug 2012 17:04:16 +0200; 7min ago Process: 2866 ExecStart=/etc/rc.d/init.d/lircmd start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/lircmd.service â 2953 lircmd $ systemctl show lircmd.service|grep PIDFile= PIDFile=/var/run/lircmd.pid $ ls -l /var/run/lircmd.pid ls: impossible d'accéder à /var/run/lircmd.pid: Aucun fichier ou dossier de ce type $ pidof lircmd 2953
Assignee: bugsquad => anssi.hannula
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD