> On 1 May 2023, at 22:41, Tom Horsley <horsley1...@gmail.com> wrote: > > On Mon, 01 May 2023 13:39:29 -0700 > Jonathan Ryshpan wrote: > >> And the problem remains. Further advice would be welcome. > > Without ever managing to determine what the problem was, I have > sometimes resorted to disabling the service, then making an > rc.local script that uses the "at" command to start the service > 10 or 20 seconds from "now".
You need ti run the program in its debug mode to show you what it is up to when it detects an error. If the code is not designed to be debugged then you could try running it under strace to find out what system call it makes that returns the EINVARG. Barry > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
