Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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
   systemd-fire-udev.service (0.7 KiB)
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.
Comment by alex (kabolt) - Tuesday, 11 February 2014, 13:24 GMT
sorry bugreport is for systemd in stable, I don't know if it is still a problem in testing
Comment by alex (kabolt) - Tuesday, 11 February 2014, 13:26 GMT
my fix is a modified systemd file (/usr/lib/systemd/system/systemd-udev-trigger.service)
Comment by Dave Reisner (falconindy) - Tuesday, 11 February 2014, 13:57 GMT
Works for me, and every other machine I've ever installed systemd on. Is this bare metal or some virtualized container?

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).

Loading...