[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-12-20 Thread Till Kamppeter
** Changed in: systemd (Ubuntu)
   Importance: High => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-21 Thread Mathew Hodson
** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-16 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-16 Thread Till Kamppeter
Reported this bug upstream:

https://github.com/systemd/systemd/issues/7109

** Bug watch added: github.com/systemd/systemd/issues #7109
   https://github.com/systemd/systemd/issues/7109

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/7109
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-13 Thread Sebastien Bacher
Till, you should perhaps open a bug on systemd upstream on github since
it's likely an issue there? There might have a clue about it or people
who are available to debug the issue...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-11 Thread Till Kamppeter
Here is the systemd journal of plugging the printer, taken with

journalctl -o verbose -f 2>&1 | tee systemd-journal-plug.log

After issuing the command (with printer unplugged) I waited some seconds
to see that there is no further output happening. Then I plugged the
printer and waited for no further output happening again and stopped the
command with Ctrl+C. Output is attached.

** Attachment added: "systemd-journal-plug.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+attachment/4967934/+files/systemd-journal-plug.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-11 Thread Till Kamppeter
Now I have proceeded as described in the previous comment for unplugging
the printer, issuing this command with the printer still plugged:

journalctl -o verbose -f 2>&1 | tee systemd-journal-unplug.log

waited some seconds, unplugged the printer, waited some seconds, Ctrl+C.
Output attached.

** Attachment added: "systemd-journal-unplug.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+attachment/4967939/+files/systemd-journal-unplug.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-11 Thread Till Kamppeter
I have tried recording startup and shutdown now by recording with the
command "sleep 10" and doing the manual operation (plugging/unplugging
USB) during the sleep delay. Unfortunately, it does not work.

For unplugging I did

sudo umockdev-record --ioctl=/dev/bus/usb/002/009=deskjet-2540-ioctl-
shutdown.log sleep 10

and unplugged the USB plug right after pressing Enter. After waiting for
the command to exit I did not get a deskjet-2540-ioctl-shutdown.log
file.

For plugging I did

sudo umockdev-record --ioctl=/dev/bus/usb/002/010=deskjet-2540-ioctl-
startup.log sleep 10

with the intention to plug the printer right after issuing the command.

Note that after repugging the printer will appear under Bus:Device
002:010 so I used /dev/bus/usb/002/010. As the printer is still
unplugged when issuing the command there is not yet a
/dev/bus/usb/002/010 file and the program exists immediately complaining
because of that and does not run "sleep 10".

So any help to record start-up and shutdown of a USB device is
appreciated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-11 Thread Till Kamppeter
I have looked through Pitti's (upstream author) instructions of the
tool, ut it seems that it only works on the already running device and
that there is no way to capture the startup and shutdown sequences.

I have recorded the main record of the device this way:

till@till-x1carbon:~$ lsusb
[...]
Bus 002 Device 009: ID 03f0:c211 Hewlett-Packard 
[...]
till@till-x1carbon:~$ sudo umockdev-record /dev/bus/usb/002/009 > 
deskjet-2540.umockdev

I have attached the file.

One can record device operations, but only those which can get triggered
by a shell command, not those who are triggered by a manual operation on
the device (plug/unplug, power-cycle, press button, ...).

Is there a shell command which triggers a shutdown, start-up, or reboot
of the printer? Especially one has to take into account that the device
keeps only its bus ID and the device ID increments by 1.

@pitti, is there a way to record start-up or shutdown of a USB device?

** Attachment added: "deskjet-2540.umockdev"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+attachment/4967899/+files/deskjet-2540.umockdev

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-11 Thread Dimitri John Ledkov
Could you please record udevmock dump of plugging in and out a USB
printer and attach the udevmock file here?

https://www.piware.de/2013/02/umockdev-record-and-mock-hardware-for-
debugging-and-testing/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-11 Thread Dimitri John Ledkov
This is not critical. The service is started, but the encoding/decoding
of the %i name appears to be not round-trip safe.

** Changed in: systemd (Ubuntu)
   Importance: Critical => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-11 Thread Dimitri John Ledkov
Given that the service is oneshot, I need a full output of the journal
to see what has happened to said service.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-10 Thread Till Kamppeter
It seems that with a 70-printers.rules as follows at least a correct
service name is generated

--
# Low-level USB device add trigger
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="'%c'"
# Low-level USB device remove trigger
ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
--

Note that in the first rule the systemd-escape command has NO "-p"
option and that the %c for ENV{SYSTEMD_WANTS} has extra single quotes.
Compared to the original file only these single quotes got added.

After restarting UDEV with

sudo udevadm control --reload

and re-plugging the printer in most cases the service does not get
started.

systemctl status 'udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2\x2d2.service' > status.txt

gives something like

--
● udev-configure-printer@devices-pci:00-:00:14.0-usb2-2\x2d2.service - 
Automatic USB/Bluetooth printer setup 
(devices-pci:00-:00:14.0-usb2-2\x2d2)
   Loaded: loaded (/lib/systemd/system/udev-configure-printer@.service; static; 
vendor preset: enabled)
   Active: inactive (dead)
--

In such a case one can start the service manually with

sudo systemctl start 'udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2\x2d2.service'

and this starts correctly udev-configure printer which sets up the
printer (and starts ippusbxd if needed).

In some very few cases the service actually gets correctly started (and
the printer set up) when one plugs the printer, but this happens rarely
(can there be some kind of race condition?).

So this only rarely happening automatic start of the printer setup
service is now the problem. The escaping seems to be fixed by the extra
single quotes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-09 Thread Till Kamppeter
** Tags added: rls-aa-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-09 Thread Till Kamppeter
Some discussion with xnox on IRC helped me to get to a possible cause of
the problem:

journalctl -u udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2x2d2.service > journalctl-u.txt

gives (file redirection prevents trimming ;lines to terminal width):

--
-- Logs begin at Mon 2017-10-09 09:07:44 -03, end at Mon 2017-10-09 12:17:45 
-03. --
Oct 09 11:29:17 till-x1carbon systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:14.0-usb2-2x2d2)...
Oct 09 11:29:17 till-x1carbon udev-configure-printer[23296]: add 
/devices/pci:00/:00:14.0/usb2/2x2d2
Oct 09 11:29:17 till-x1carbon udev-configure-printer[23296]: unable to access 
/sys/devices/pci:00/:00:14.0/usb2/2x2d2
Oct 09 11:29:17 till-x1carbon systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2x2d2.service: 
Control process exited, code=exited status=1
Oct 09 11:29:17 till-x1carbon systemd[1]: Failed to start Automatic 
USB/Bluetooth printer setup (-devices-pci:00-:00:14.0-usb2-2x2d2).
Oct 09 11:29:17 till-x1carbon systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2x2d2.service: 
Unit entered failed state.
Oct 09 11:29:17 till-x1carbon systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2x2d2.service: 
Failed with result 'exit-code'.
--

The directory which needs to get accessed by udev-configure-printer is:
/sys/devices/pci:00/:00:14.0/usb2/2-2, note that the second last
character is a dash. UDEV/systemd(?) inserts for the %i in the second
line of the /lib/systemd/system/udev-configure-printer@.service file:
-devices-pci:00-:00:14.0-usb2-2x2d2, replacing each slash by a
dash and the original dash by "x2d" (should it not be "\x2d"? Not sure
what gets inserted for the %I in the ExecStart line, but udev-configure-
printer ends up with a /sys/devices/pci:00/:00:14.0/usb2/2x2d2
which it does not find as the "x2d" is not turned back into a dash.

This worked in 17.04 so it is a regression.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs