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

Jump to bottom

Updating caused sddm to be reenabled,started, and its tty focused #104

Closed
michaelmrose opened this issue Sep 17, 2020 · 1 comment
Closed

Updating caused sddm to be reenabled,started, and its tty focused #104

michaelmrose opened this issue Sep 17, 2020 · 1 comment

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@michaelmrose @beanpole135
@michaelmrose
Copy link

@michaelmrose michaelmrose commented Sep 17, 2020

I switched to lightdm among other reasons because sddm froze a few times and failed to recognize i3-wm as an available session. I disabled sddm by removing its symlink in /var/service when running xbps-install -Su to update packages it was surprising to me re enabled, started, and I was switched to its tty which was pretty confusing.

Thanks for all your efforts!
@beanpole135
Copy link
Member

@beanpole135 beanpole135 commented Sep 18, 2020

This is intentional as a basic functionality of the "trident-desktop" package to ensure that all the required services (such as sddm) are enabled after an upgrade.

If you are switching all of the "desktop" functionality around to other login managers or desktop environments, I highly recommend removing the "trident-desktop" meta-package from your system to prevent this issue in the future - since you are basically trying to disable that package after-the-fact anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment