Description of problem: Booting to multiuser leaves a severely crippled system because hald gets a trace/breakpoint trap and does not initialize devices (keyboard, network, ...)
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
1. boot to multi-user (level 3 or level 5)
"Starting HAL demon: /bin/bash: line 1: Trace/breakpoint trap"
and the network is not up (and "ifup eth0" complains that eth0 is not present), and there is no response to keyboard.
Expected results: Normal multi-user system with keyboard and network.
This is reportedly an SELinux issue "triggered by the change in gobject to enable threads by default".
It's thought to be fixed in selinux-policy-3.7.8-5.fc13:
I can confirm the bug and the fix here: no input (even at runlevel 3, for me...) with today's Rawhide, the updated selinux-policy fixes it. Added a note to Rawhide Watch:
This is fixed in Rawhide now.