Bug 2165692

Summary: Booting to multi-user.target and then doing 'systemctl isolate graphical.target' does not work with systemd 253
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 38CC: dtardon, fedoraproject, filbranden, lnykryn, msekleta, ryncsn, systemd-maint, yuwatana, zbyszek
Target Milestone: ---Keywords: Regression, Reopened, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: openqa
Fixed In Version: systemd-253~rc2-7.fc39 systemd-253~rc2-7.fc38 systemd-253~rc3-1.fc39 systemd-253~rc3-1.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-13 16:12:26 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 Flags
journal messages from a boot reproducing the issue none

Description Adam Williamson 2023-01-30 19:18:25 UTC
Since systemd 253~rc1 landed in Rawhide in Fedora-Rawhide-20230125.n.0 , booting to the console (with boot arg `3` or `systemd.unit=multi-user.target`) and then running `systemctl isolate graphical.target` to bring up the graphical environment does not work (neither with GNOME nor KDE). The system shows a blinking cursor on a blank screen. Switching to any other VT shows the same thing (except VT9, if you boot with the debug shell enabled).

This is a problem for openQA, which uses this approach on a test where it wants to do something at the console before the graphical environment starts up at all.

Comment 1 Adam Williamson 2023-01-30 19:19:28 UTC
Created attachment 1941147 [details]
journal messages from a boot reproducing the issue

Comment 2 Ben Cotton 2023-02-07 15:07:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 3 Zbigniew Jędrzejewski-Szmek 2023-02-09 22:10:31 UTC
systemd-253~rc2-7.fc39 is building now. In my testing, it resolves the issue.

Comment 4 Fedora Update System 2023-02-09 22:19:17 UTC
FEDORA-2023-1e2657220e has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1e2657220e

Comment 5 Fedora Update System 2023-02-09 22:24:13 UTC
FEDORA-2023-1e2657220e has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2023-02-09 22:40:06 UTC
FEDORA-2023-d81081a762 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d81081a762

Comment 7 Fedora Update System 2023-02-09 23:48:23 UTC
FEDORA-2023-d81081a762 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Zbigniew Jędrzejewski-Szmek 2023-02-10 17:52:31 UTC
The build I did yesterday didn't actually apply the patch. I'll submit -rc3
shortly that has a different solution that was also confirmed to resolve the issue.

Comment 9 Fedora Update System 2023-02-13 15:59:39 UTC
FEDORA-2023-ad9ba1ade6 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ad9ba1ade6

Comment 10 Fedora Update System 2023-02-13 16:07:26 UTC
FEDORA-2023-d48a58478d has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d48a58478d

Comment 11 Fedora Update System 2023-02-13 16:12:26 UTC
FEDORA-2023-d48a58478d has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2023-02-13 16:27:14 UTC
FEDORA-2023-ad9ba1ade6 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.