Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gdm remains after this installation of tbsm #5

Open
zzzgit opened this issue Aug 18, 2018 · 6 comments
Open

gdm remains after this installation of tbsm #5

zzzgit opened this issue Aug 18, 2018 · 6 comments

Comments

@zzzgit
Copy link

zzzgit commented Aug 18, 2018

image

how can I ensure that?

@loh-tar
Copy link
Owner

loh-tar commented Aug 18, 2018

That depends on your distribution. So you should consult there documentation.

In general it may usual to remove the other, not needed, package. But it may sufficient to disable the other display manager. On systemd based installations it is something like systemctl disable <foobar>.service. Perhaps there are more steps needed.

I'm sorry that I can't guide you in all detail because I'm not a Linux-Guru. In all not daily tasks I have to study the Arch-Wiki.

@brunelli
Copy link
Contributor

Maybe this line should be updated with something like:

NOTE: Ensure you start no other display manager. You can check your distribution's
documentation for disabling system services or uninstalling packages.

@loh-tar
Copy link
Owner

loh-tar commented Mar 2, 2019

Yes, will add this hint.
Furthermore I will add an Tips&Tricks section to the doc. So when someone has an detailed advice how to get rid of other manager on some system, please let me know.

@sandboiii
Copy link

sandboiii commented Apr 28, 2019

@loh-tar as said in the arch wiki

a symlink display-manager.service should be set in /etc/systemd/system/

So, in systemd based distribution to ensure no other display manager used one should examine the /etc/systemd/system directory for existance of display-manager.service symlink.

But this sure to work only for Arch Linux, other distributions might be using other directories for systemd.
So, this check should be done with listing services command to the systemd manager like this:

systemctl list-unit-files | grep display-manager

Also it would be nice if tbsm had it's own service enabling which would override other display managers and somehow make tbsm working without manual configuring any shells. But this seems hard to implement

@sandboiii
Copy link

sandboiii commented Apr 28, 2019

Basically to remove display manager one should disable it's service via command like this:

# systemctl disable display-manager.service

But as far as I know in Ubuntu display manager services are static, which means they can not be disabled nor enabled. To change the display manager one should reconfigure them with command like this:

# dpkg-reconfigure gdm

Where gdm is curently active display manager. To completely disable display managers in Ubuntu there are some steps to complete

@loh-tar
Copy link
Owner

loh-tar commented Apr 29, 2019

Thanks Alexey,

I guess you note this here in reference to my "please let me know". ATM I will not update my docu, just kept this ticket open :-)

Also it would be nice if tbsm had it's own service enabling which would
override other display managers and somehow make tbsm working without manual
configuring any shells. But this seems hard to implement

Yes, could be difficult. But if someone has a patch, fine.

I think, even tbsm is named this way, it isn't a truer display manager. tbsl may more fitting, session launcher. But cdm/tdm are also named this way, so I didn't want to break the history or insinuate tbsm can do less then these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants