Bugzilla – Bug 707418
Using systemd at boot, system starts in runlevel 3 (no X) instead of runlevel 5
Last modified: 2011-09-15 11:37:54 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 I am using a vanilla GNOME system (12.1, M3) installed on virtualbox. I am using systemd at startup using the grub-menu (F5), however that leads to my installed system starting up in text mode (runlevel 3) instead of runlevel 5. While using the traditional bootup it happens correctly to run level 5. I am not sure what logs to attache for this report. Thanks Reproducible: Always Steps to Reproduce: 1. 2. 3.
I should add that, once the system has booted into runlevel 3, it is possible thereafter to log in as root and start X (using init 5 as usual) and the system then functions correctly, i.e. X starts up, so does Gdm, etc.
I also saw this effect 100% reproducible on Factory and openQA tests with all desktop environments. I found that /etc/init.d/xdm is not started at boot at all. Calling it later manually makes gdm/kdm/lxdm start up normally. example failure: http://openqa.opensuse.org/results/openSUSE-NET-i586-Build0167-lxde remains on console after reboot_lxde
This is because systemd package is now installed during the install phase, but /etc/inittab is modified by installer after systemd package is installed and default runlevel change is not reflected to /etc/systemd/system/default.target (it should be a symlink to /lib/systemd/system/runlevel5.target and not /lib/systemd/system/runlevel3.target, for graphical login). installer should update the link itself.
I think yast2 runlevel should be aware of systemd changing the link manually resolve my trouble for X
until Yast installer is fixed, I've implemented a workaround : systemd will now automatically create a default.target symlink at startup, based on /etc/inittab default runlevel value, if /etc/systemd/system/default.target doesn't exist. Keeping this bug opened, so we don't forget Yast need to be fixed.
This is an autogenerated message for OBS integration: This bug (707418) was mentioned in https://build.opensuse.org/request/show/79689 Factory / systemd
I'll fix the Yast part.
Fixed in yast2-runlevel-2.21.0. Frederic, you can remove the workaround (comment #5).
This is an autogenerated message for OBS integration: This bug (707418) was mentioned in https://build.opensuse.org/request/show/81015 Factory / yast2 https://build.opensuse.org/request/show/81016 Factory / yast2-runlevel
Thanks Ladislav, I'll remove the workaround in systemd (also we might still keep it, your change will take precedence over my workaround ;)
Found that recent DVD/NET installs had a wrong /etc/systemd/system/default.target symlink to runlevel3.target for both KDE and GNOME installs. When changing it manually to runlevel5.target, KDE started properly.
Bernhard, could you attach y2log from the installation?
Created attachment 450817 [details] yast2 logs
According to the log it seems that there was used some older yast2-runvel package (the line numbers in the log do match the latest code). The bug has been fixed in 2.21.0 version. Bernhard, could check the package version?
you are right, the /.packages.root contains yast2-runlevel 2.20.1-5.3.noarch instsys timestamp is 20110831 so instsys needs to be updated/rebuilt for things to work
OK, so I'm resolving it as FIXED, reopen if you can still reproduce it using updated instsys.