Bug 828197
| Summary: | systemctl start graphical.target => finishes firstboot but then gdm does not offer a login, only a spinning circle cursor | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Wendell Baker <wendellcraigbaker> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | johannbg, metherid, mschmidt, msekleta, notting, plautrba, satellitgo, systemd-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-06-15 16:05:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Wendell Baker
2012-06-04 12:48:01 UTC
Created attachment 589137 [details]
/var/log/messages #1 as referenced in the initial bug description
Created attachment 589138 [details]
/var/log/messages #2 as referenced in the initial bug description
Created attachment 589140 [details]
/var/log/messages #1 as referenced in the initial bug description
Created attachment 589148 [details]
/var/log/messages #1 as referenced in the initial bug description
Created attachment 589149 [details]
/var/log/messages #2 as referenced in the initial bug description
As it may come up ...
The machine was configured as:
$ ls -l /etc/systemd/system/default.target
lrwxrwxrwx. 1 root root 36 Jun 3 12:26 /etc/systemd/system/default.target -> /lib/systemd/system/runlevel3.target
To get to a graphical login (runlevel 5) one is supposed to do:
$ sudo rm /etc/systemd/system/default.target
$ sudo ln -s /lib/systemd/system/graphical.target /etc/systemd/system/default.target
$ ls -l /etc/systemd/system/default.target
lrwxrwxrwx. 1 root root 36 Jun 4 06:08 /etc/systemd/system/default.target -> /lib/systemd/system/graphical.target
I was confused thinking that "systemctl enable graphical.target" did this or should have done this. Perhaps a more helpful diagnostic sequence is indicated here:
$ sudo systemctl is-enabled graphical.target
disabled
$ sudo systemctl enable graphical.target
Failed to issue method call: File exists
The correct enablement activity is documented in /etc/inittab
Boot to gdm login occurs. So what remains it's unclear why gdm won't come up in that first scenario after the firstboot workflow completes.
(In reply to comment #0) > $ sudo systemctl enable graphical.target > Failed to issue method call: File exists Yes, it won't overwrite an existing default.target symlink pointing to a different target. Using "-f" would force it to overwrite. The error message could be improved. As to why gdm did not come up after firstboot, I don't know. Fedora-18-x86_64-Live-SoaS.iso (RC1) does not startx after firstboot -leaves spinning cursor (In reply to comment #8) > Fedora-18-x86_64-Live-SoaS.iso (RC1) does not startx after firstboot -leaves > spinning cursor also Fedora-18-i686-Live-SoaS.iso confirmed in install of RC4 Soas-live x86_64 finishes firstboot but then gdm does not offer a login, only a spinning circle cursor A new administrator command line switch has been introduced in systemctl , upstream to change the default boot target and get/list the default boot target ( http://cgit.freedesktop.org/systemd/systemd/commit/?id=99504dd4c ) Which should be used and address this issue. Any firstboot/gdm issues should be filed against the correct component if still present. |