Bug 631018

Summary: cannot change from "runlevel" 3 to "runlevel" 5
Product: [Fedora] Fedora Reporter: Mamoru TASAKA <mtasaka>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-07 16:34:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mamoru TASAKA 2010-09-07 16:02:53 UTC
Description of problem:
With
- /etc/systemd/system/default.target pointing to 
  /lib/systemd/system/runlevel3.target

When I
- reboot, boot with systemd
- login on tty1 as root
- type # telinit 5 or # systemctl isolate graphical.target
then nothing happens (i.e. gdm never launches)

Version-Release number of selected component (if applicable):
systemd-8-3.fc14.i686
kernel-2.6.35.4-18.fc14.i686
dbus-1.4.0-1.fc14.i686

How reproducible:
100%

Steps to Reproduce:
1. See above
2.
3.
  
Expected results:
With upstart, when
- reboot with runlevel 3
- login on tty1 as root
- type # telinit 5
will cause gdm to launch.

Additional info
With systemd, 
- reboot with targeting multi-user.target
- login on tty1 as root
- type # systemctl rescue
  -> after this login passwd is required (bug 628929)
- then # systemctl isolate graphical.target
will cause gdm to launch (i.e. with systemd, going to "runlevel 5" will
require to once go down to "runlevel 1")

Comment 1 Michal Schmidt 2010-09-07 16:34:57 UTC

*** This bug has been marked as a duplicate of bug 627014 ***