Arch Linux

Rye

Member

Registered: 2016-08-11

Posts: 3

Is there a way to regain control of tty1 after stopping the DM ?

Just a curiosity, since I do have tty2 trough 6 to keep doing what I'm doing...
If I stop the DM on tty1 on Arch, I see all the [OK] notifications from the boot sequence, and the terminal is just stuck there.
I had the same thought on other distros, where if I stopped the display manager (To change it or whatever reason....) I would end up with a black screen on tty7, until I restarted it or until I started a new one.

P.S. Hi everyone ! Just got here

Last edited by Rye (2016-08-11 22:56:09)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,715

Re: Is there a way to regain control of tty1 after stopping the DM ?

As a sanity check, did you try hitting Enter or Return on tty1?

Oh, and welcome to the Arch Linux Forums

Edit:  As to screen 7.  A lot of distributions (including this one I think) instantiate six consoles on the ttys.  Traditionally  7 and up were used for Xorg.  Now we put the X session on the log in terminal.  What you are seeing on tty1 is not what you were seeing on tty7 on the other distros.

Last edited by ewaller (2016-08-11 14:26:29)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: Is there a way to regain control of tty1 after stopping the DM ?

If I stop the DM on tty1

Which commands are you using to do this?

EDIT: Nice avatar!

Last edited by Head_on_a_Stick (2016-08-11 20:58:11)

---

Jin, Jîyan, Azadî

Rye

Member

Registered: 2016-08-11

Posts: 3

Re: Is there a way to regain control of tty1 after stopping the DM ?

As a sanity check, did you try hitting Enter or Return on tty1?
Oh, and welcome to the Arch Linux Forums

Yep, I tried that XD
(And thanks !)

Which commands are you using to do this?
EDIT: Nice avatar! big_smile

systemctl stop lxdm.service

systemctl disable lxdm.service

To stop it, and disable it at boot... do I need to do something else ?
(And thanks to you too )

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: Is there a way to regain control of tty1 after stopping the DM ?

Have you tried:

# systemctl isolate multi-user.target

and:

# systemctl set-default multi-user.target

To make this the default.

Last edited by Head_on_a_Stick (2016-08-13 10:08:51)

---

Jin, Jîyan, Azadî

Rye

Member

Registered: 2016-08-11

Posts: 3

Re: Is there a way to regain control of tty1 after stopping the DM ?

Have you tried:

# systemctl isolate multi-user.target

and:

# systemctl set-default multi-user.target

To make this the default.

If I force a runlevel 3 like this I have the opposite problem:
I immediately regain control of tty1 (without a reboot) but when I try to go back with

# systemctl isolate graphical.target

or

# lxdm

etc.
when I log in, these errors pop up:

Unable to contact settings server
Failed to connect to socket /run/user/0/bus: Permission denied

Unable to get connection to the message bus session
Failed to connect to socket /run/user/0/bus: Permission denied

And I'm forced to reboot

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: Is there a way to regain control of tty1 after stopping the DM ?

A quick scan of the relevant ArchWiki page shows that:

LXDM does not support the XDMCP protocol

https://wiki.archlinux.org/index.php/LXDM

Perhaps this would explain your problems.

Do the issues still occur if you switch to LightDM?

We use that in BunsenLabs and it seems to play nicely with systemd.

---

Jin, Jîyan, Azadî