We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Expected behavior For lightdm to run when I run it
Actual behavior Lightdm doesnt run, and systemctl status lightdm says
● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-12-18 22:31:43 EST; 1min 15s ago Docs: man:lightdm(1) Process: 19759 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Process: 19762 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Main PID: 19762 (code=exited, status=1/FAILURE) Dec 18 22:31:43 prometheus systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2. Dec 18 22:31:43 prometheus systemd[1]: Stopped Light Display Manager. Dec 18 22:31:43 prometheus systemd[1]: lightdm.service: Start request repeated too quickly. Dec 18 22:31:43 prometheus systemd[1]: lightdm.service: Failed with result 'exit-code'. Dec 18 22:31:43 prometheus systemd[1]: Failed to start Light Display Manager.
Steps To Reproduce
sudo systemctl start lightdm
Additional context I can run it from test mode, but not from systemd
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected behavior
For lightdm to run when I run it
Actual behavior
Lightdm doesnt run, and systemctl status lightdm says
Steps To Reproduce
sudo systemctl start lightdm
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I can run it from test mode, but not from systemd
The text was updated successfully, but these errors were encountered: