** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
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/1625217
Title:
udev sometimes doesn't apply systemd tag to
** Attachment added: "Output of 'udevadm info --export-db' from a good boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751947/+files/udev-db.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "Output of 'udevadm info --export-db' from a failed boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751945/+files/udev-db.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "Output of 'journalctl -xb' from a failed boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751944/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Attachment added: "Output of 'journalctl -xb' from a good boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751946/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This is still happening, and it feels like a race. I've enabled debug
logging and captured the journal from good and bad boots. Comparing them
hasn't told me a whole lot; on the whole the udev debug logging isn't
very applicable. I do see that in both cases udev starts up and reads
the exact same
** Attachment added: "Output of 'udevadm info --export-db'"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4743665/+files/udev-db.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
7 matches
Mail list logo