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

2016-07-18 Thread Robert M. Koretsky 
Martin:
Sounds good, thanks for the info about systemctl stop lightdm!
Robert M. Koretsky

On Sun, Jul 17, 2016 at 10:41 PM, Martin Pitt 
wrote:

> 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 subscribed to the bug
> report.
> 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
>

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-18 Thread Robert M. Koretsky 
Martin:
Yes, that's all that remains of this for me. But it's no big deal to hold
down Ctrl-Alt-F2 to switch to tty2.
Robert M. Koretsky

On Sun, Jul 17, 2016 at 10:40 PM, Martin Pitt 
wrote:

> So to summarize, the only problem is that stopping lightdm does not
> change the VT back to 1 or 2 or something sensible, but stays at 7 where
> no getty ("login:") is running so it might *appear* crashed?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-17 Thread Martin Pitt 
So to summarize, the only problem is that stopping lightdm does not
change the VT back to 1 or 2 or something sensible, but stays at 7 where
no getty ("login:") is running so it might *appear* crashed?

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-17 Thread 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603151

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-17 Thread Robert M. Koretsky 
Martin:
After systemctl isolate multi-user.target, I could ssh into the machine.
Also, after systemctl isolate multi-user.target, then Ctrl-Alt-F2, I could
login on tty2.
Proof that the system didn't hang or crash.
I could then systemctl isolate graphical.target and was back in the
beautiful Cinnamon Desktop!
That's a fix for me.
My graphics card is whatever comes standard on the motherboard of an HP
Proliant Microserver.
I've attached the requested journal log files.
I will experiment with switching to rescue and emergency targets work as
well.
Initially, I was doing the systemctl isolate on a Mint 18 guest running in
VirtualBox. I could ssh into the VirtualBox guest, but couldn't figure out
how to use Ctrl-Alt-F2 in the guest. The above session was done on Mint 18
running on bare metal on the HP.
Thanks very much for helping to solve my problem!
Sincerely,
Robert M. Koretsky


On Sun, Jul 17, 2016 at 2:17 PM, Martin Pitt 
wrote:

> > 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.
>
> That sounds like the command actually worked, but stopping lightdm and
> thus the graphics driver breaks the state of the graphics card. Does
> changing VTs with Ctrl-Alt-F2 work? If not, please check if you can
> still log into the system with ssh (I suppose that works), and capture
> "sudo journalctl -b > /tmp/journal.txt" and "systemctl status >
> /tmp/status.txt" and attach the files here. Also, which graphics
> driver/card are you using? Please don't file bugs direectly in
> Launchpad, use "ubuntu-bug" for this (this will automatically attach
> information about your hardware).
>
> > 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.
>
> Ubuntu does not modify the upstream unit, and it does have
> AllowIsolate=yes. "CanIsolate" does not exist.
>
> ** Changed in: systemd (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1603151
>
> Title:
>   systemctl isolate anyname.target not working
>
> Status in systemd package in Ubuntu:
>   Incomplete
>
> 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/systemd/+bug/1603151/+subscriptions
>


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/1603151/+attachment/4702550/+files/journal.txt

** Attachment added: "status.txt"
   https://bugs.launchpad.net/bugs/1603151/+attachment/4702551/+files/status.txt

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

Title:
  systemctl isolate anyname.target not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-17 Thread Martin Pitt 
> 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.

That sounds like the command actually worked, but stopping lightdm and
thus the graphics driver breaks the state of the graphics card. Does
changing VTs with Ctrl-Alt-F2 work? If not, please check if you can
still log into the system with ssh (I suppose that works), and capture
"sudo journalctl -b > /tmp/journal.txt" and "systemctl status >
/tmp/status.txt" and attach the files here. Also, which graphics
driver/card are you using? Please don't file bugs direectly in
Launchpad, use "ubuntu-bug" for this (this will automatically attach
information about your hardware).

> 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.

Ubuntu does not modify the upstream unit, and it does have
AllowIsolate=yes. "CanIsolate" does not exist.

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

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

Title:
  systemctl isolate anyname.target not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs