From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 Description of problem: during reboot of FC3T2 after latest update this AM, got msg /sbin/start_udev unexpected } in line 79. Then get a series of error msgs that went by too fast to catch. On this multi-boot computer, booted into FC2 and in /var/log/messages saw a lot of X failures. Will attach todays messages and boot logs. Result is that a graphical logon never appears. Can blindly logon, then blindly C-A-F2 and blindly logon as root then reboot. Version-Release number of selected component (if applicable): udev-032-2 How reproducible: Always Steps to Reproduce: 1.boot latest FC3T2 2. 3. Actual Results: Never got a graphical logon screen. Expected Results: Normal logon Additional info: Downgraded to libbonoboui-2.8.0-1 yesterday to fix Evolution and eggcups problems.
Created attachment 104515 [details] boot log from today Shows various efforts to boot today.
Created attachment 104517 [details] messages from today's boot attempts
Created attachment 104518 [details] X log from today
Created attachment 104519 [details] another X log from today
Can boot into runlevel 3 to do maintenance work. startx goes to blank screen and keyboard is lifeless.
There is a missing 'fi' line in start_udev that when added back fixes this error allowing machine to boot fine. mount_udev() { if [ -z "$SELINUX" ]; then if [ -n "$selinuxfs" ] && [ "`cat /proc/self/attr/current`" != "kernel" ]; then if [ -r $selinuxfs/enforce ] ; then SELINUX=`cat $selinuxfs/enforce` else # assume enforcing if you can't read it SELINUX=1 fi fi fi ^^ omitted 'fi'
Made the change. No longer see the start_udev error, but still get the X failures. Can still go into runlevel 3 on boot and can get to FC3T2 partition from FC2. SELinux was and is turned off.
Syntax error fixed in 032-5.
*** Bug 134161 has been marked as a duplicate of this bug. ***
I did an interactive boot so I could see and record some of the messages that don't show in the logs and saw the following: starting mDNSResponder... /etc/profile: line 27: /dev/null: Permission denied /etc/profile.d/colorls.sh: line 3: /dev/null: Permission denied (above msg wa repeated for lines 4, 17, 18, 19 and 20) /etc/profile.d/vim.sh: line 3: /dev/null: Permission denied [howl] unable to daemonize (3419) . . . starting atd: [FAILED] Did the bad udev corrupt something else?
Downgraded udev to 032-2. Strange that the patch above didn't work. Wonder what caused all the problems.
I added the 'fi' in the right place and everything now works for me. I'm using 2.8.1 kernel build 590.
udev-032-5 should work
i'm installed udev-032-5 and reboot, then get this: Making extra nodes: cp: cannot stat '/etc/udev/devices/*': No such file or directory Starting udev: [FAILED]
comment #14 is fixed in udev-032-6
*** Bug 134255 has been marked as a duplicate of this bug. ***
Except for comment 13, 032-5 is working fine for me.
except from comment #14 (Making extra nodes: cp: cannot stat '/etc/udev/devices/*': No such file or directory), udev-032-5 works for me