[Bug 1603151] Re: systemctl isolate anyname.target not working

[Martin Pitt]

This is the same with "systemctl stop lightdm", btw. I'm reassigning
this to lightdm.

** Summary changed:

- systemctl isolate anyname.target not working
+ stopping lightdm ends up in an empty console, should switch to VT1

** Package changed: systemd (Ubuntu) => lightdm (Ubuntu)

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Low

** Changed in: lightdm (Ubuntu)
       Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1603151

Title:
  stopping lightdm ends up in an empty console, should switch to VT1

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu 16.04 Cinammon, systemctl isolate multi-user.target hangs the system.
  I've tried editing the multi-user.target file as a snippet, or the whole thing, but with no fix.
  The system flashes a very momentary prompt to login as a single user without a GUI, but then the screen goes black and the system is hung.
  Same on Linux Mint 18.
  systemctl isolate multi-user.target works successfully on OpenSuse Leap 42.1, and CentOS 7, as I tested the command on these other systems to check. The glaring difference I noticed is that in the multi-user.target unit file, AllowIsolate and CanIsolate is set to yes in the other Linux systems, but to no in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1603151/+subscriptions