FS#38872 - [systemd] doesn't fire udev add event on start
Attached to Project:
Arch Linux
Opened by alex (kabolt) - Tuesday, 11 February 2014, 13:20 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 11 February 2014, 14:00 GMT
Opened by alex (kabolt) - Tuesday, 11 February 2014, 13:20 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 11 February 2014, 14:00 GMT
|
Details
Description:
My udev scripts didn't worked so I had a look inside and found out that the systemd unit for firing an udev event on boot isn't started (I use encryption and lvm may this is the problem) Quickfix: systemd unit which fires udev events when started see atachment |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 11 February 2014, 14:00 GMT
Reason for closing: Works for me
Additional comments about closing: Not a bug, ask for support on the forums.
Tuesday, 11 February 2014, 14:00 GMT
Reason for closing: Works for me
Additional comments about closing: Not a bug, ask for support on the forums.
Your proposed "fix" is wrong, anyways. systemd-udev-trigger is ordered to run before sysinit.target which is reached, and needed, well before basic.target.
You should look into which portion of the upstream unit file isn't satisfied for you, and then figure out why *that* unit isn't activated. It's likely some local modification you made because there's no chance I can reproduce this bug on a fresh install (or the install media).