Open leana8959 opened 3 months ago
I don't believe this is causing systemd-udev to fail, but does cause an error message in the logs.
On my system, systemctl status systemd-udevd
shows the service is active (running)
. I do see those errors in the journal as well.
Thank you for your quick reply !
In fact, I noticed that when I run scanimage -L
, my scanner isn't detected. However, running the same command with sudo works. I suspect that there might be something wrong with the udev file, I filed the bug report when I saw that it's not recognizing the SYSFS key.
Is it expected for scanimage -L
to only work when run as root or is it somehow related to this issue ?
Thanks :)
You probably need the scanner
and possibly lp
group as stated in the desc for hardware.sane.enable
Describe the bug
When using the
hardware.sane.brscan5
option, the udev rule supplied by the upstream contains the deprecated key "SYSFS".This cause
systemd.udevd.service
to fail.Steps To Reproduce
Steps to reproduce the behavior: First set
Then run
Expected behavior
brscan5
's udev rule shouldn't failsystemd-udevd.service
.Additional context
I did a quick grep on the latest (brscan5-1.3.5-0.amd64.deb) upstream package, the offending "SYSFS" key is still present. Maybe we need to patch this ourselves for now ?
Notify maintainers
@mattchrist
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a :+1: reaction to issues you find important.