Description of problem: udev 166-1 breaks the boot on my laptop. It appears to be logging related - booting with 'LogLevel=debug' shows lots of messages about the logger exiting. Then there's a 60 second or so wait, and all the 'mount' jobs exit with a 'failed timeout'. Things then go pear-shaped because /usr isn't mounted. Reverting to udev-164 allows my laptop to boot. I suspect the issue is related to /dev/log creation somehow. Version-Release number of selected component (if applicable): udev 166-1.fc16 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
/dev/kmsg or /dev/log ??
OK, I changed the summary... Actually, it's unclear which - I said /dev/kmsg when I opened the problem, then realized that /dev/kmsg was probably OK since I was seeing the systemd 'LogLevel=debug' output in dmesg. But I can't even tell easily whether it's /lib/systemd/systemd-logger or systemd-kmsg-syslogd that's having the indigestion. Part of the debugging problem is that the 'retrigger failed events' phase seems to clean up the wreckage, so everything *looks* OK once you get up to single-user mode. I'll pop -166 back on the laptop and catch the dmesg output later this evening and attach it to the bug report, hopefully you'll be able to see something I'm missing.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
still a problem?
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Not sure why this bug is still open, am closing because it got fixed somehow 3 years ago (not sure what the fix/resolution was)