Skip to content

fix: Repeatedly running "systemctl isolate graphical.target" will cause unexpected problems - #16548

Closed
husjdodoanthing wants to merge 1 commit into
systemd:masterfrom
husjdodoanthing:master
Closed

husjdodoanthing wants to merge 1 commit into
systemd:masterfrom
husjdodoanthing:master

Conversation

@husjdodoanthing

Copy link
Copy Markdown

There are two issues that will be dealt with here:

  1. If the current system running level is graphical.target, when you run "systemctl isolate graphical.target" in the terminal again, switching tty 2~6 at this time will cause the display screen to collapse.
  2. The second situation is when multiple users log in and the system run level is 5. When a user runs "systemctl isolate graphical.target" in the terminal, the system will return to the startup interface, and any operation will be invalid , Only forcibly restart the system to solve this problem...

@husjdodoanthing husjdodoanthing changed the title fix: Repeatedly running will cause unexpected problems fix: Repeatedly running systemctl isolate graphical.target will cause unexpected problems Jul 23, 2020
@husjdodoanthing husjdodoanthing changed the title fix: Repeatedly running systemctl isolate graphical.target will cause unexpected problems fix: Repeatedly running "systemctl isolate graphical.target" will cause unexpected problems Jul 23, 2020
@keszybz

keszybz commented Jul 23, 2020

Copy link
Copy Markdown
Member

No, this is not a fix. isolate has various issues, let's discuss that in the ticket. Nonetheless, this just papers over one specific problem and is not something that we can apply. In particular, nothing in the definition of isolate says that you cannot isolate to the same run level twice.

@keszybz keszybz closed this Jul 23, 2020
@keszybz

keszybz commented Jul 23, 2020

Copy link
Copy Markdown
Member

Oh, for some reason I thought that there's a separate issue and a pull request. I'll continue the comment here.

The answer is to simply not run isolate. In general, isolate is a low level operation that only makes sense in very very specific circumstances and generally doesn't work as people might want it to. See e.g.#2607 for previous discussions. I know that we say in the man page that it's equivalent to switching run levels. We probably shouldn't do that and that would be one thing to fix.

keszybz added a commit to keszybz/systemd that referenced this pull request Jul 23, 2020
We need to do better here, but for now let's at least not trick
users into nuking their graphical environment. Inspired by systemd#16548.
@husjdodoanthing

Copy link
Copy Markdown
Author

@keszybz
Thank you very much. I had to make this modification because there were many unexpected problems in the use of isolate, but I did not solve the root problem, just circumvent the problem. If there are new ideas, I will continue to communicate with you, thank you for your answer!

keszybz added a commit that referenced this pull request Jul 23, 2020
We need to do better here, but for now let's at least not trick
users into nuking their graphical environment. Inspired by #16548.
vbatts pushed a commit to kinvolk/systemd that referenced this pull request Nov 12, 2020
We need to do better here, but for now let's at least not trick
users into nuking their graphical environment. Inspired by systemd#16548.

(cherry picked from commit 5cf821a)
vbatts pushed a commit to kinvolk/systemd that referenced this pull request Nov 12, 2020
We need to do better here, but for now let's at least not trick
users into nuking their graphical environment. Inspired by systemd#16548.

(cherry picked from commit 5cf821a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants