Fedora Account System
Red Hat Associate
Red Hat Customer
The spacenavd daemon log messages end up getting added to /var/log/messages instead of going to the systemd journal for the spacenavd.service unit. The configuration in the service unit file contains this line: > [Service] > ... > StandardError=syslog The stderr logs should probably be redirected to the journal. In order to do this, I added a local service unit for spacenavd whose contents are as follows: > [Unit] > After= > > [Service] > Type= > Type=exec > ExecStart= > ExecStart=/usr/bin/spacenavd -d -l /dev/stdout > StandardOutput= > StandardError= As you can see, I removed the dep on syslog as well as redirecting the logs to stdout so that they can be captured by the journal. I think this is probably a better config in a systemd world. Reproducible: Always Steps to Reproduce: 1. Start spacenavd.service unit Actual Results: Log messages go to /var/log/messages via syslog Expected Results: Log messages land in the systemd journal
Created attachment 2095627 [details] A diff for rawhide branch in the repo at https://src.fedoraproject.org/rpms/spacenavd.git
And updated local service unit to get rid of all the warnings that system was giving that I just noticed: > # /etc/systemd/system/spacenavd.service.d/override.conf > [Unit] > After= > > [Service] > Type=exec > PIDFile=/run/spnavd.pid > ExecStart= > ExecStart=/usr/bin/spacenavd -d -l /dev/stdout > StandardError=journal The previously attached diff is in line with the local override.
Put up https://src.fedoraproject.org/rpms/spacenavd/pull-request/1 for this
FEDORA-2025-bbf9786307 (spacenavd-1.3.1-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-bbf9786307
FEDORA-2025-bbf9786307 (spacenavd-1.3.1-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.