Bug#693522: systemd: Doing init 5 from runlevel 1 will result in an unusable system
Hi Salvo, Salvo Tomaselli wrote (06 Jan 2013 11:47:45 GMT) : # systemctl status systemd-logind.service [...] Thanks for providing this additional information. However, it seems that more Michael's questions were not answered yet: Do you have any services in failed state when you switch back to the multi-user runlevel? Do yo have any error messages in the log files? ... so I'm leaving the moreinfo tag set for now. Also, it might be useful to try and reproduce this problem on current sid. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693522: systemd: Doing init 5 from runlevel 1 will result in an unusable system
Hi, Just tried on Sid to do init 1 and then init 5. Can confirm the problem. Virtual terminals seem to be gone, i just have one X11 session, pressing ctrl+alt+F* doesn't do anything. My CPU is 100% used by /sbin/agetty Best root@hal9000:/home/salvo# systemctl status systemd-logind.service systemd-logind.service - Login Service Loaded: loaded (/lib/systemd/system/systemd-logind.service; static) Active: active (running) since mer 2014-06-25 14:45:53 CEST; 4min 52s ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 12894 (systemd-logind) CGroup: name=systemd:/system/systemd-logind.service └─12894 /lib/systemd/systemd-logind giu 25 14:45:53 hal9000 systemd[1]: Starting Login Service... giu 25 14:45:53 hal9000 systemd-logind[12894]: Watching system buttons on /dev/input/event1 (Power Button) giu 25 14:45:53 hal9000 systemd-logind[12894]: Watching system buttons on /dev/input/event12 (Video Bus) giu 25 14:45:53 hal9000 systemd-logind[12894]: Watching system buttons on /dev/input/event0 (Lid Switch) giu 25 14:45:53 hal9000 systemd-logind[12894]: Watching system buttons on /dev/input/event3 (ThinkPad Extra Buttons) giu 25 14:45:54 hal9000 systemd-logind[12894]: New session c1 of user salvo. giu 25 14:45:54 hal9000 systemd-logind[12894]: Linked /tmp/.X11-unix/X0 to /run/user/1001/X11-display. This is what I found in syslog from systemd: Jun 25 14:45:40 localhost systemd[1]: Stopping Disk Manager... Jun 25 14:45:53 localhost systemd[1]: Stopping Rescue Mode. Jun 25 14:45:53 localhost systemd[1]: Stopped target Rescue Mode. Jun 25 14:45:53 localhost systemd[1]: Stopping Rescue Shell... Jun 25 14:45:53 localhost systemd[1]: Starting Login Service... Jun 25 14:45:53 localhost systemd[1]: Starting Forward Password Requests to Wall Directory Watch. Jun 25 14:45:53 localhost systemd[1]: Started Forward Password Requests to Wall Directory Watch. Jun 25 14:45:53 localhost systemd[1]: Starting Login Prompts. Jun 25 14:45:53 localhost systemd[1]: Reached target Login Prompts. Jun 25 14:45:53 localhost systemd[1]: Starting D-Bus System Message Bus... Jun 25 14:45:53 localhost systemd[1]: Started D-Bus System Message Bus. Jun 25 14:45:53 localhost systemd[1]: Starting /etc/rc.local Compatibility... Jun 25 14:45:53 localhost systemd[1]: Started LSB: Starts or stops the lapdog daemon.. Jun 25 14:45:54 localhost systemd[1]: Starting Mail Transport Agent. Jun 25 14:45:54 localhost systemd[1]: Reached target Mail Transport Agent. Jun 25 14:45:54 localhost systemd[1]: Starting LSB: init-Script for system wide fetchmail daemon... Jun 25 14:45:54 localhost systemd[1]: Started LSB: init-Script for system wide fetchmail daemon. Jun 25 14:45:54 localhost systemd[1]: Started /etc/rc.local Compatibility. Jun 25 14:45:54 localhost systemd[1]: Starting Console Manager... Jun 25 14:45:54 localhost dbus[12895]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service' Jun 25 14:45:54 localhost dbus[12895]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service' Jun 25 14:45:54 localhost systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks... Jun 25 14:45:54 localhost systemd[1]: Started Authenticate and Authorize Users to Run Privileged Tasks. Jun 25 14:45:54 localhost systemd[1]: Started Console Manager. Jun 25 14:45:55 localhost dbus[12895]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' Jun 25 14:45:55 localhost systemd[1]: Starting Daemon for power management... Jun 25 14:45:55 localhost systemd[1]: Started Daemon for power management. Jun 25 14:45:55 localhost dbus[12895]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Jun 25 14:45:55 localhost systemd[1]: Starting Disk Manager... Jun 25 14:45:55 localhost systemd[1]: Started Disk Manager. Jun 25 14:45:58 localhost systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details. Jun 25 14:45:58 localhost systemd[1]: Stopping Disk Manager... Jun 25 14:45:58 localhost systemd[1]: Stopping Daemon for power management... Jun 25 14:45:58 localhost systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks... Jun 25 14:45:58 localhost systemd[1]: Stopping Console Manager... Jun 25 14:45:58 localhost systemd[1]: Started Manage Sound Card State (restore and store). Jun 25 14:45:58 localhost systemd[1]: Starting Restore Sound Card State... Jun 25 14:45:58 localhost systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. Jun 25 14:45:58 localhost systemd[1]: Started Set Up Additional Binary Formats. Jun 25
Bug#693522: systemd: Doing init 5 from runlevel 1 will result in an unusable system
Hi, Salvo Tomaselli wrote (25 Jun 2014 12:53:53 GMT) : Can confirm the problem. Virtual terminals seem to be gone, i just have one X11 session, pressing ctrl+alt+F* doesn't do anything. Thanks for confirming. To address the other question of Michael's, I think that providing the output of `systemctl list-units --failed', run after switching back to multi-user runlevel, might help. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693522: systemd: Doing init 5 from runlevel 1 will result in an unusable system
To address the other question of Michael's, I think that providing the output of `systemctl list-units --failed', run after switching back to multi-user runlevel, might help. # systemctl list-units --failed 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693522: systemd: Doing init 5 from runlevel 1 will result in an unusable system
ping? Sorry I forgot about this bug! # systemctl status systemd-logind.service systemd-logind.service - Login Service Loaded: loaded (/lib/systemd/system/systemd-logind.service; static) Active: active (running) since Sun, 06 Jan 2013 12:37:59 +0100; 2min 46s ago Main PID: 3629 (systemd-logind) CGroup: name=systemd:/system/systemd-logind.service └ 3629 /lib/systemd/systemd-logind Jan 06 12:37:59 hal9000 systemd-logind[3629]: New seat seat0. Jan 06 12:38:00 hal9000 systemd-logind[3629]: New session c1 of user salvo. Jan 06 12:38:00 hal9000 systemd-logind[3629]: Linked /tmp/.X11-unix/X0 to /run/user/salvo/X11-display. Jan 06 12:38:58 hal9000 systemd-logind[3629]: New session c2 of user root. So it seems normal. Anyway I experience a lot of different behaviors. - Giving init 1 from a terminal within KDE sometimes works but can also lead to a normal login prompt where the keyboard input is ignored and then i must hard-reset. - If i give init 1 from outside X11, it seems to be working. - Sometimes giving init 5 from single user mode works correctly. - Other time it doesn't and i see a mouse cursor and a blinking text cursor in the corner, then pressing ctrl+alt+F1 it goes to normal KDE, but i don't seem to have any non-X11 sessions available (despite the service seems to be running). In this situation also the fan seems to be running more than it's fair share but there are no greedy processes showing up in top. Bye -- Salvo Tomaselli UNIT LOAD ACTIVE SUB JOB DESCRIPTION proc-sys...misc.automount loaded inactive dead Arbitrary Executable File Formats File System Automount Point dev-cdrom3.device loaded active plugged SlimtypeDVD_A_DS8A5SH dev-cdrw3.device loaded active plugged SlimtypeDVD_A_DS8A5SH dev-disk...0343575.device loaded active plugged SlimtypeDVD_A_DS8A5SH dev-disk...81A5694.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart1.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart2.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart3.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart4.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...81A5694.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart1.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart2.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart3.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart4.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...bb06000.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart1.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart2.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart3.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart4.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk..._MAG_71.device loaded active plugged SlimtypeDVD_A_DS8A5SH dev-disk...0:0:0:0.device loaded active plugged SlimtypeDVD_A_DS8A5SH dev-disk...2dpart1.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart2.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart3.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...2dpart4.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...6113d5b.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...8FFA4AB.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...e8bfe4a.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-disk...e184635.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-dvd3.device loaded active plugged SlimtypeDVD_A_DS8A5SH dev-dvdrw3.device loaded active plugged SlimtypeDVD_A_DS8A5SH dev-root.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-sda.deviceloaded active plugged WDC_WD5000BPVT-08HXZT1 dev-sda1.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-sda2.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-sda3.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-sda4.device loaded active plugged WDC_WD5000BPVT-08HXZT1 dev-sr0.deviceloaded active plugged SlimtypeDVD_A_DS8A5SH dev-tty0.device loaded active plugged /dev/tty0 dev-tty1.device loaded active plugged /dev/tty1 dev-tty10.device loaded active plugged /dev/tty10 dev-tty11.device loaded active plugged /dev/tty11 dev-tty12.device loaded active plugged /dev/tty12 dev-tty2.device loaded
Bug#693522: systemd: Doing init 5 from runlevel 1 will result in an unusable system
On 17.12.2012 05:00, Michael Biebl wrote: What's the output of systemctl status systemd-logind.service ? Do you have any services in failed state when you switch back to the multi-user runlevel? Do yo have any error messages in the log files? ping? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#693522: systemd: Doing init 5 from runlevel 1 will result in an unusable system
tags 693522 + moreinfo unreproducible thanks On 17.11.2012 15:04, Salvo Tomaselli wrote: Package: systemd Version: 44-5 Severity: normal Tags: upstream Dear Maintainer, I am using the systemd-sysv, but the issue is identical if i use the sysvinit init implementation. Starting the system normally, and giving init 1 it will correctly go to rescue mode and ask for the root password to proceed. Inserting the root password and then just typing init 5 will result in a very odd situation: I can not reproduce this problem. init 1 (or telinit 1) drops me to the rescue shell. If I then login and use init 5 (or telinit 5) then I'm brought back to the graphical gdm login prompt where I can login succefully. Everything is working as expected. The output of /sbin/runlevel in this case is S 5. Your route problems look like they are wicd specific. With NM I don't get such a situation. Virtual terminal are working fine here, too. They are started on demand as I switch to them. What's the output of systemctl status systemd-logind.service ? Do you have any services in failed state when you switch back to the multi-user runlevel? Do yo have any error messages in the log files? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#693522: systemd: Doing init 5 from runlevel 1 will result in an unusable system
Package: systemd Version: 44-5 Severity: normal Tags: upstream Dear Maintainer, I am using the systemd-sysv, but the issue is identical if i use the sysvinit init implementation. Starting the system normally, and giving init 1 it will correctly go to rescue mode and ask for the root password to proceed. Inserting the root password and then just typing init 5 will result in a very odd situation: - Blank screen, blinking cursor at the top left corner, but an X11 pointer shows. - After that, pressing ctrl+alt+F1 will take me to KDM. - I can login to KDE normally. - Whatever ctrl+alt+F* combination i use, i will only see my KDE session, no virtual terminals. - Despite wicd up and running, route -n will show that the gateway is not set. (Okay i could set it manually or do something about it myself). The non working virtual terminals are annoying and i have no clue how to make them reappear except for a reboot. Bye -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6.6a (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii dpkg 1.16.9 ii initscripts 2.88dsf-34 ii libacl1 2.2.51-8 ii libaudit01:1.7.18-1.1 ii libc62.13-36 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.4.3-4 ii libdbus-1-3 1.6.8-1 ii libkmod2 9-2 ii liblzma5 5.1.1alpha+20120614-1 ii libpam0g 1.1.3-7.1 ii libselinux1 2.1.9-5 ii libsystemd-daemon0 44-5 ii libsystemd-id128-0 44-5 ii libsystemd-journal0 44-5 ii libsystemd-login044-5 ii libudev0 175-7.1 ii libwrap0 7.6.q-24 ii udev 175-7.1 ii util-linux 2.20.1-5.2 Versions of packages systemd recommends: pn libpam-systemd none Versions of packages systemd suggests: ii python2.7.3-3 ii python-cairo 1.8.8-1+b2 ii python-dbus 1.1.1-1 pn systemd-gui none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
