[Touch-packages] [Bug 910272] Re: USB->Parallel adapter produces crappy device URI and CUPS "usb" backend cannot cope with it

2020-08-19 Thread Bill Yikes
Same problem for me. I have an old parallel-only printer. It has been working with a dedicated printer server, but the printer server died and the PC has no parallel port. So I connected a USB-to-LPT cable. As I attach the cable /var/log/syslog shows: parport0: fix this legacy no-device port

[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed

2020-08-08 Thread Bill Yikes
Bug report to improve debugging output: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890890 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890836 Title: udev

[Touch-packages] [Bug 1890890] [NEW] more debugging verbosity for udev rules needed

2020-08-08 Thread Bill Yikes
Public bug reported: I wrote a udev rule that would not trigger when expected. I spent 2 days working on it, trying to understand what the problem was. I finally figured it out -- it was a matching problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836 The most verbose output

[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed

2020-08-08 Thread Bill Yikes
PEBKAC ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Bill Yikes (yik3s) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in

[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed

2020-08-08 Thread Bill Yikes
It turns out the problem arises out of cargo cult programming on my part. The bang in KERNEL=="sd*[!0-9]" is what I copied out of stackexchange, and it's exactly what prevents the mount from matching. I suspected that early on, but ruled it out because when the device first connects it must

[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed

2020-08-07 Thread Bill Yikes
It fails for me on two different systems: * Ubuntu 20.04 (Focal) * Linux Mint 19.2 (Tina, which is based on Bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890836

[Touch-packages] [Bug 1890836] [NEW] udev rule read but "RUN" command is not executed

2020-08-07 Thread Bill Yikes
Public bug reported: The following was introduced as "/etc/udev/rules.d/99-harvest_camera.rules": ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D", RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh" When the device is attached, it gets mounted but the

[Touch-packages] [Bug 1890520] Re: catastrophic bug with deluser command -- destroys large number of system files

2020-08-07 Thread Bill Yikes
Notice also there is a serious transparency problem. The output only shows files for which removal failed. This acutely heightens the destruction because it potentially destroyed *thousands* of files as I sat there and let it run. The tool gives no idea how what's being destroyed. The admin

[Touch-packages] [Bug 1890827] [NEW] udev and udevadm documentation missing

2020-08-07 Thread Bill Yikes
Public bug reported: The man page for udevadm neglects to mention options which seem to only be documented in stackexchange. E.g. udevadm monitor --environment udevadm control --reload-rules >From the man page, it's unclear what the difference is between /udevadm trigger/ and /udevadm test/.

[Touch-packages] [Bug 1890654] Re: udev service does not log

2020-08-07 Thread Bill Yikes
Sorry, i mean to say /var/log/syslog (not /var/log/system) shows the device was attached. The verbosity in /var/log/syslog increases when udev_log=debug, but still no /var/log/udev. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is