# journalctl -b -u tdm -- Logs begin at Sat 2019-06-22 02:01:13 EDT, end at Fri 2020-02-21 02:23:16 EST. -- Feb 21 02:22:42 p5bse systemd[1]: Started The Trinity login manager. Feb 21 02:22:43 p5bse systemd[1]: tdm.service: Main process exited, code=exited, status=1/FAILURE Feb 21 02:22:43 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:22:43 p5bse systemd[1]: tdm.service: Scheduled restart job, restart counter is at 1. Feb 21 02:22:43 p5bse systemd[1]: Stopped The Trinity login manager. Feb 21 02:22:43 p5bse systemd[1]: Started The Trinity login manager. Feb 21 02:22:43 p5bse systemd[1]: tdm.service: Main process exited, code=exited, status=1/FAILURE Feb 21 02:22:43 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Scheduled restart job, restart counter is at 2. Feb 21 02:22:44 p5bse systemd[1]: Stopped The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: Started The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Main process exited, code=exited, status=1/FAILURE Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Scheduled restart job, restart counter is at 3. Feb 21 02:22:44 p5bse systemd[1]: Stopped The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: Started The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Main process exited, code=exited, status=1/FAILURE Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Scheduled restart job, restart counter is at 4. Feb 21 02:22:44 p5bse systemd[1]: Stopped The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: Started The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Main process exited, code=exited, status=1/FAILURE Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Scheduled restart job, restart counter is at 5. Feb 21 02:22:44 p5bse systemd[1]: Stopped The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Start request repeated too quickly. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:22:44 p5bse systemd[1]: Failed to start The Trinity login manager. # systemctl status tdm ● tdm.service - The Trinity login manager Loaded: loaded (/usr/lib/systemd/system/tdm.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2020-02-21 02:40:49 EST; 1min 10s ago Process: 568 ExecStart=/opt/trinity/bin/kdm (code=exited, status=1/FAILURE) Main PID: 568 (code=exited, status=1/FAILURE) CPU: 6ms
Feb 21 02:40:49 p5bse systemd[1]: tdm.service: Scheduled restart job, restart counter is at 5. Feb 21 02:40:49 p5bse systemd[1]: Stopped The Trinity login manager. Feb 21 02:40:49 p5bse systemd[1]: tdm.service: Start request repeated too quickly. Feb 21 02:40:49 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:40:49 p5bse systemd[1]: Failed to start The Trinity login manager.
Startx won't successfully start a TDE session, but it will an IceWM session. Xorg.0.log contains no EE clues, and there is no ~/.xsession-errors. PC is about 12 years old, Core2Duo.
Any suggestions how to debug this?
On Friday 21 of February 2020 08:45:25 Felix Miata wrote:
Feb 21 02:22:44 p5bse systemd[1]: Started The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Main process exited, code=exited, status=1/FAILURE Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Scheduled restart job, restart counter is at 5. Feb 21 02:22:44 p5bse systemd[1]: Stopped The Trinity login manager. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Start request repeated too quickly. Feb 21 02:22:44 p5bse systemd[1]: tdm.service: Failed with result 'exit-code'. Feb 21 02:22:44 p5bse systemd[1]: Failed to start The Trinity login manager. # systemctl status tdm ● tdm.service - The Trinity login manager Loaded: loaded (/usr/lib/systemd/system/tdm.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2020-02-21 02:40:49 EST; 1min 10s ago Process: 568 ExecStart=/opt/trinity/bin/kdm (code=exited, status=1/FAILURE) Main PID: 568 (code=exited, status=1/FAILURE) CPU: 6ms
Feb 21 02:40:49 p5bse systemd[1]: tdm.service: Scheduled restart job, restart counter is at 5. Feb 21 02:40:49 p5bse systemd[1]: Stopped The Trinity login manager.
Hi Felix,
the listing shows that there is mistake in /usr/lib/systemd/system/tdm.service - there is /opt/trinity/bin/kdm instead of /opt/trinity/bin/tdm.
I thought François had already fixed this in the package. Do you have up to date packages? Alternatively, you can fix it in the script, regardless of the package update.
Cheers
Slávek Banko composed on 2020-02-21 09:25 (UTC+0100):
Felix Miata wrote:
...
ExecStart=/opt/trinity/bin/kdm (code=exited, status=1/FAILURE) Main PID: 568 (code=exited, status=1/FAILURE)
...
the listing shows that there is mistake in /usr/lib/systemd/system/tdm.service - there is /opt/trinity/bin/kdm instead of /opt/trinity/bin/tdm.
I thought François had already fixed this in the package. Do you have up to date packages?
It resulted from a dnf upgrade. # ls -l /usr/lib/systemd/system/tdm.service -rw-r--r-- 1 root root 266 Jan 1 16:34 tdm.service # rpm -qf /usr/lib/systemd/system/tdm.service trinity-tdm-14.0.7-1.fc31.x86_64 # dnf upgrade trinity-tdm ... Nothing to do.
Alternatively, you can fix it in the script, regardless of the package update.
Editing the file on disk fixed it. :-)
-
Felix Miata -
Slávek Banko