Bug 1625948 - systemctl set-default graphical.target doesn't effective
Summary: systemctl set-default graphical.target doesn't effective
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 31
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-06 09:25 UTC by xhe@redhat.com
Modified: 2020-08-01 13:57 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-08-01 13:57:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
boot.log (12.51 KB, application/octet-stream)
2018-09-06 09:25 UTC, xhe@redhat.com
no flags Details
dmesg.log (54.04 KB, text/plain)
2018-09-06 09:26 UTC, xhe@redhat.com
no flags Details

Description xhe@redhat.com 2018-09-06 09:25:31 UTC
Created attachment 1481242 [details]
boot.log

Description of problem:
systemctl set-default graphical.target doesn't effective and work, I have to start X by manual everytime on fedora 27

Version-Release number of selected component (if applicable):
$ cat /etc/redhat-release 
Fedora release 27 (Twenty Seven)

$ uname -r
4.17.19-100.fc27.x86_64

$ rpm -qa|grep usermode
usermode-1.112-3.fc27.x86_64

How reproducible:
often

Steps to Reproduce:
1. Install fedora 27
2. upgrade system to the latest with dnf or yum
3. system lost the X after boot up

Actual results:
X can NOT work after system boot up, I have to executed 'startx' every time. I checked the boot.log and dmesg, I didn't see any ERROR or FAIL there.

Expected results:
X is not started automatically

Additional info:

Comment 1 xhe@redhat.com 2018-09-06 09:26:35 UTC
Created attachment 1481243 [details]
dmesg.log

Comment 2 Ben Cotton 2019-08-13 16:57:42 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 3 Ben Cotton 2019-08-13 19:44:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 4 Jiri Kucera 2019-12-03 14:36:11 UTC
It looks like that the affected component is systemd, but I am not 100% sure about it. usermode just provides userhelper program which allows configured programs to be run with superuser privileges by ordinary users (it is a predecessor of polkit/D-Bus).

Comment 5 Zbigniew Jędrzejewski-Szmek 2019-12-03 16:33:42 UTC
Dunno, why do you think it's not effective? What does 'systemctl get-default' say?

Note that the attached boot.log is from an unfinished boot, so not everything
that has been queued to be started was started at the time the log ends.


Note You need to log in before you can comment on or make changes to this bug.