summaryrefslogtreecommitdiff
path: root/debian/TROUBLESHOOTING.Debian
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff-webhosting.net>2020-09-27 12:48:48 +0200
committerJörg Frings-Fürst <debian@jff-webhosting.net>2020-09-27 12:48:48 +0200
commitc8ad32f887472f2e0be3fd24a9e94be82f11a5c8 (patch)
treeeeb983875aabc3f7587d65248d5c61b10db4cca8 /debian/TROUBLESHOOTING.Debian
parentbee56be23c98b5324b7897612a9fa9742fae82de (diff)
Fix some trailing whitespaces / blank lines
Diffstat (limited to 'debian/TROUBLESHOOTING.Debian')
-rw-r--r--debian/TROUBLESHOOTING.Debian12
1 files changed, 6 insertions, 6 deletions
diff --git a/debian/TROUBLESHOOTING.Debian b/debian/TROUBLESHOOTING.Debian
index 423d9e8..f96469f 100644
--- a/debian/TROUBLESHOOTING.Debian
+++ b/debian/TROUBLESHOOTING.Debian
@@ -9,21 +9,21 @@ If you get this error meessage you can try
echo -e "\nblacklist usblp" >> /etc/modprobe.d/blacklist.conf
-and reboot. After that your scanner can used.
+and reboot. After that your scanner can used.
-REMARK: Sometimes usblp is used to access your printer.
+REMARK: Sometimes usblp is used to access your printer.
2.) ACL: device file system does not support ACLs
From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789593
-The file /etc/udev/rules.d/99-libsane1.rules uses the command "/bin/setfacl -m g:scanner:rw
+The file /etc/udev/rules.d/99-libsane1.rules uses the command "/bin/setfacl -m g:scanner:rw
$env{DEVNAME}" to add the "scanner" group with rw access to the device permissions.
-In my case, with /dev on an ext4 filesystem with no ACL support enabled in the kernel, setfacl
-returns "Operation not supported". I assume this is because it's trying to add a group, which is not
+In my case, with /dev on an ext4 filesystem with no ACL support enabled in the kernel, setfacl
+returns "Operation not supported". I assume this is because it's trying to add a group, which is not
possible in its fallback mode of traditional Unix-style file permissions.
-As a workaround, I have substituted "/bin/chown root:scanner $env{DEVNAME}" as the command at the
+As a workaround, I have substituted "/bin/chown root:scanner $env{DEVNAME}" as the command at the
end of 99-libsane1.rules (an alternative would be to use a UDEV rule element to change the ownership).