Hide Forgot
Description of problem: Complete hang up Version-Release number of selected component (if applicable): Fedora 16 How reproducible: Always Steps to Reproduce: 1. go to runlevel 1 2. go back to 5 3. on the console let the first login fail 4. give the right credentials Actual results: Systems hangs forever (well I turned it off after 3 hours and numerous Ctrl-Cs) Expected results: I should have got a shell. Additional info: The last bit of /var/log/messages (before the hard reset) Jan 11 14:51:59 kind audispd: audispd initialized with q_depth=120 and 1 active plugins Jan 11 14:51:59 kind abrtd: Init complete, entering main loop Jan 11 14:51:59 kind systemd-logind[1960]: New seat seat0. Jan 11 14:51:59 kind auditd[1964]: Init complete, auditd 2.1.3 listening for events (startup state enable) Jan 11 14:51:59 kind systemd[1]: Failed to read PID file /var/run/iscsid.pid after start. The service might be broken. Jan 11 14:52:00 kind network[2018]: Bringing up loopback interface: [ OK ] Jan 11 14:52:00 kind network[2018]: Bringing up interface Wired_connection_1: RTNETLINK answers: File exists Jan 11 14:52:00 kind network[2018]: RTNETLINK answers: File exists Jan 11 14:52:00 kind network[2018]: ERROR : [ipv6_add_addr_on_device] Cannot add IPv6 address '2a01:198:5b7:200::18/64' on dev 'eth0' Jan 11 14:52:00 kind ipv6_add_addr_on_device: Cannot add IPv6 address '2a01:198:5b7:200::18/64' on dev 'eth0' Jan 11 14:52:00 kind NET[2232]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf Jan 11 14:52:00 kind network[2018]: [ OK ] Jan 11 14:52:01 kind systemd[1]: Failed to read PID file /var/run/fcoemon.pid after start. The service might be broken. Jan 11 14:52:01 kind rpc.statd[2274]: Version 1.2.5 starting Jan 11 14:52:01 kind sm-notify[2275]: Version 1.2.5 starting Jan 11 14:52:01 kind sm-notify[2275]: Already notifying clients; Exiting! Jan 11 14:52:02 kind autofs[2252]: Starting automount: [ OK ] Jan 11 14:52:02 kind systemd[1]: prefdm.service: main process exited, code=exited, status=1 Jan 11 14:52:02 kind systemd[1]: prefdm.service holdoff time over, scheduling restart. Jan 11 14:52:02 kind systemd[1]: Unit prefdm.service entered failed state. Jan 11 14:52:02 kind systemd[1]: prefdm.service: main process exited, code=exited, status=1 Jan 11 14:52:02 kind systemd[1]: prefdm.service holdoff time over, scheduling restart. Jan 11 14:52:02 kind systemd[1]: Unit prefdm.service entered failed state. Jan 11 14:52:03 kind systemd[1]: prefdm.service: main process exited, code=exited, status=1 Jan 11 14:52:03 kind systemd[1]: prefdm.service holdoff time over, scheduling restart. Jan 11 14:52:03 kind systemd[1]: Unit prefdm.service entered failed state. Jan 11 14:52:03 kind systemd[1]: prefdm.service: main process exited, code=exited, status=1 Jan 11 14:52:03 kind systemd[1]: prefdm.service holdoff time over, scheduling restart. Jan 11 14:52:03 kind systemd[1]: Unit prefdm.service entered failed state. Jan 11 14:52:03 kind systemd[1]: prefdm.service: main process exited, code=exited, status=1 Jan 11 14:52:03 kind systemd[1]: prefdm.service holdoff time over, scheduling restart. Jan 11 14:52:03 kind systemd[1]: Unit prefdm.service entered failed state. Jan 11 14:52:03 kind systemd[1]: prefdm.service: main process exited, code=exited, status=1 Jan 11 14:52:03 kind systemd[1]: prefdm.service holdoff time over, scheduling restart. Jan 11 14:52:03 kind systemd[1]: Unit prefdm.service entered failed state. Jan 11 14:52:03 kind systemd[1]: prefdm.service start request repeated too quickly, refusing to start. Jan 11 14:52:05 kind dbus[1995]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Jan 11 14:52:05 kind dbus-daemon[1995]: dbus[1995]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Jan 11 14:52:05 kind dbus-daemon[1995]: Launching FprintObject Jan 11 14:52:05 kind dbus-daemon[1995]: dbus[1995]: [system] Successfully activated service 'net.reactivated.Fprint' Jan 11 14:52:05 kind dbus[1995]: [system] Successfully activated service 'net.reactivated.Fprint' Jan 11 14:52:05 kind dbus-daemon[1995]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Jan 11 14:52:05 kind dbus-daemon[1995]: ** Message: entering main loop Jan 11 14:52:36 kind dbus-daemon[1995]: ** Message: No devices in use, exit Jan 11 14:52:41 kind systemd[1]: Failed to read PID file /run/sendmail.pid after start. The service might be broken. Jan 11 14:52:41 kind dbus[1995]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Jan 11 14:52:41 kind dbus-daemon[1995]: dbus[1995]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Jan 11 14:52:41 kind dbus-daemon[1995]: Launching FprintObject Jan 11 14:52:41 kind dbus-daemon[1995]: dbus[1995]: [system] Successfully activated service 'net.reactivated.Fprint' Jan 11 14:52:41 kind dbus[1995]: [system] Successfully activated service 'net.reactivated.Fprint' Jan 11 14:52:41 kind dbus-daemon[1995]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Jan 11 14:52:41 kind dbus-daemon[1995]: ** Message: entering main loop Jan 11 14:53:13 kind kernel: imklog 5.8.5, log source = /proc/kmsg started. Jan 11 14:53:13 kind rsyslogd: [origin software="rsyslogd" swVersion="5.8.5" x-pid="748" x-info="http://www.rsyslog.com"] start Jan 11 14:53:12 kind mcelog.setup[714]: read: No such device Jan 11 14:53:13 kind alsactl[709]: /sbin/alsactl: load_state:1586: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
(In reply to comment #0) > Steps to Reproduce: What is the initial state? Being in runlevel 5 and logged in an X session? > 1. go to runlevel 1 Here you may already encounter bug 771563, which is fixed in systemd-37-6.fc16. > 2. go back to 5 > 3. on the console let the first login fail Not sure what you mean exactly. CTRL+ALT+F<n> to switch to a text VT and give a bad username/password? > 4. give the right credentials On the same VT? Try if systemd-37-6.fc16 changes anything for you. https://admin.fedoraproject.org/updates/systemd-37-6.fc16
Oh sorry. The initial runlevel is 5, state is an xdm running, and a serial console is attached from which I'm performing my diagnostics. Yes, correct credentials on the same VT, can't be more precise as it's all the serial console in my case. I'll try the fix, and report back.
Ok, now it's a bit easier to reproduce the bug. With 37-6.fc16 it's not necessary to give the wrong credentials anymore. The system hangs even if the first credentials are correct. (Or maybe that was always the case but with a systemd 36 it seemed to work if the credentials were correct right away)
what's the conntent of /etc/sysconfig/desktop ? i got this issue also, but i fixed, cuz i allways install Fedora from minimal packages options on install stage and every time i forgot to config /etc/sysconfig/desktop, i think this skips firstlogin and other setup which could be the issue of not having /etc/sysconfig/desktop created which could lead to this "bug") [root@lxvz9mv901 ~]# uname -a Linux lxvz9mv901 3.3.7-1.fc17.i686.PAE #1 SMP Mon May 21 22:42:05 UTC 2012 i686 i686 i386 GNU/Linux [root@lxvz9mv901 ~]# rpm -q openbox lxdm openbox-3.5.0-5.fc17.i686 lxdm-0.4.1-1.fc17.i686 [root@lxvz9mv901 ~]# and i got solved as soon as created /etc/sysconfig/desktop here you have mine: [root@lxvz9mv901 ~]# cat /etc/sysconfig/desktop PREFERRED=/usr/bin/openbox-session DISPLAYMANAGER=/usr/sbin/lxdm [root@lxvz9mv901 ~]#
Correct. That indeed `fixes' the problem.
This is handled by the spins ks files as in "# LXDE and LXDM configuration # create /etc/sysconfig/desktop (needed for installation) cat > /etc/sysconfig/desktop <<EOF PREFERRED=/usr/bin/startlxde DISPLAYMANAGER=/usr/sbin/lxdm EOF" # xfce configuration # create /etc/sysconfig/desktop (needed for installation) cat > /etc/sysconfig/desktop <<EOF PREFERRED=/usr/bin/startxfce4 EOF etc.. Thus closing this as a notabug Thanks.
And where is that documented? I think it's rather odd to assume there is a /etc/sysconfig/desktop present, and if there's not, to freeze the system. But ok, I will file a bug elsewhere then.
This is handled by the spins? ....dont think so... if you install from dvd-iso choosing the minimal installation, and from then install your custom X-server and display manager you wont have the /etc/sysconfig/desktop configured, so, you'll be in trouble. But this is opensource, so, you can allways google it or check /etc/X11/prefdm to see what it does. ;-)
It it just go through the desktop spins here... http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=tree;h=31a20c8a3a6520ced84847fa15e571b6cb83e425;hb=31a20c8a3a6520ced84847fa15e571b6cb83e425