This advice has helped alot to clear up the issue. I was able to use
chmod to clear up the permission rights.
-rw-r--r-- 1 root root 603 Apr 16 02:48
60-brother-brscan4-libsane-type1.rules
-rw-r--r-- 1 root root 760 Apr 16 02:49 60-brother-libsane-type1-inst.rules
I then edited both of the following files:
60-brother-brscan4-libsane-type1.rules
60-brother-libsane-type1-inst.rules
I commented out the following entry in each file by adding #: ->
"#SYSFS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
When I executed command: -> "sudo udevadm control --reload-rules &&
udevadm trigger" it did not seem to reload udev rules so I did reboot.
Now "journalctl -b" does not show problems with libsane or brscan4
permissions or SYSFS key.
Thanks for your excellent assistance.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
As for the execute bit (first one)
usually a 'sudo chmod -x <filepath> should do solve that warning.
The others are as I understand, be ignored.
But you should inform the related package maintainers responsible for
these files or send a message to the company support (brother/ HP) to
inform them.
Sane-devel is, I don't think, not responsible for these files, correct
me if I'm wrong.
Jōrn-Ingo Weigert
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On 4/16/21 1:54 AM, Thierry Huchard wrote:
Le 2021-04-15 23:53, [email protected] a écrit :
I decided to review the "journalctl -b" command output of my desktop
computer and came upon the following entries each after one another in
lines 983-986. I have linuxmint 20.1 installed.
Apr 14 15:04:24 user-HP-ProDesk-405-G1-MT systemd-udevd[494]:
Configuration file
/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules is marked
executable. Please remove executable permission bits. Proceeding anyway.
Apr 14 15:04:24 user-HP-ProDesk-405-G1-MT systemd-udevd[494]:
/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9 Invalid key
'SYSFS'
Apr 14 15:04:24 user-HP-ProDesk-405-G1-MT systemd-udevd[494]:
/etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14 Invalid key
'SYSFS'
Would you possibly have any suggestion on how I should or could address
the messages?
Your file does not have adequate rights, the udev rules are not
executable files and are owned by root:
# sudo chown root:root /etc/udev/rules.d/60-brother-libsane-type1.rules
# sudo chmod 0644 /etc/udev/rules.d/60-brother-libsane-type1.rules
These two commands will restore the rights of the file!
SYSFS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
ATTRS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
The two lines above verify that the usb device is a brother brand,
SYSFS does not exist or no longer exists as attributes, I suggest you
delete the line. The work is done by the remaining line:
ATTRS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
# sudo udevadm control --reload-rules && udevadm trigger
This command allows you to reload udev rules without rebooting!
Thierry
Thanks
