TDE desktop environment not loading after login

[rrf2024]

My issue is very similar of viewtopic.php?t=158739 , so I basically used his same subject.

A quick background: I used to be a fan of KDE, until they released the 4.0 version (circa 2009). Fortunatelly, Pearson created a fork from KDE3.5 as TDE and I'm using it since then.
Ubuntu has been my choice since always, but at it's 14 release, in 2020, I didn't know why, there was no TTYs available. I felt insecure about it, so I gave Debian a try.

Last Sunday, due to a power down (blackout) from a strong rain, my Debian is not logging in anymore. It crashes when trying to open X server so it opens the login screen again.

When I researched, some people had similar problem due to try opening X server with sudo or root user, thus, the .Xauthority (and/or .ICEauthority) file gets the ownership of root; denying access to normal users. (solution: chown or delete the file) But it was not my case. Also, because Debian 10 doesn't use this system anymore; it uses "MIT-MAGIC-COOKIE" in the /tmp directory.

So, here what's my /var/log/syslog has to say about it: (the relevant part)

Code: Select all

[...]
Apr 20 13:30:58 debian systemd[1]: Started User Manager for UID 1000.
Apr 20 13:30:58 debian systemd[1296]: Started kited autostart on first login of a user.
Apr 20 13:30:58 debian systemd[1296]: Reached target Default.
Apr 20 13:30:58 debian systemd[1296]: Startup finished in 564ms.
Apr 20 13:30:58 debian systemd[1]: Started Session c1 of user USER.
Apr 20 13:30:58 debian systemd-timesyncd[707]: Timed out waiting for reply from [2606:4700:f1::123]:123 (2.debian.pool.ntp.org).
Apr 20 13:30:58 debian systemd[1]: tdm.service: Main process exited, code=killed, status=11/SEGV
Apr 20 13:30:58 debian kernel: [   77.052361] show_signal_msg: 17 callbacks suppressed
Apr 20 13:30:58 debian kernel: [   77.052366] tdm[1032]: segfault at 70 ip 0000558f503ae22c sp 00007fffad34a830 error 4 in tdm[558f50397000+1e000]
Apr 20 13:30:58 debian kernel: [   77.052380] Code: 5a af ff ff 48 8b 45 f8 48 89 c7 e8 7d 86 ff ff 90 c9 c3 55 48 89 e5 48 83 ec 10 48 8b 05 84 28 01 00 48 89 45 f8 48 8b 45 f8 <8b> 40 70 83 f8 05 0f 87 f2 00 00 00 89 c0 48 8d 14 85 00 00 00 00
Apr 20 13:30:59 debian systemd[1296]: Started D-Bus User Message Bus.
Apr 20 13:30:59 debian systemd[1]: tdm.service: Failed with result 'signal'.
Apr 20 13:30:59 debian systemd[1]: tdm.service: Service RestartSec=100ms expired, scheduling restart.
Apr 20 13:30:59 debian systemd[1]: tdm.service: Scheduled restart job, restart counter is at 1.
Apr 20 13:30:59 debian systemd[1]: Stopped Trinity Display Manager.
Apr 20 13:30:59 debian systemd[1]: Starting Trinity Display Manager...
Apr 20 13:30:59 debian systemd[1]: Started Trinity Display Manager.
Apr 20 13:31:03 debian dbus-daemon[1325]: [session uid=1000 pid=1325] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.5' (uid=1000 pid=1418 comm="/usr/bin/ibus-daemon --daemonize --xim ")
Apr 20 13:31:03 debian systemd[1296]: Starting Virtual filesystem service...
[...]

and here's what my ~/.xsessions-errors has to say about it: (the file last lines)

Code: Select all

[...]
[starttde] Starting starttde.
[starttde] This script is /opt/trinity/bin/starttde
[starttde] TDE version is R14.0.13
[starttde] TDE base directory is /opt/trinity
[starttde] TDEHOME is not set.
[starttde] Set TDEHOME to /home/USER/.trinity.
[starttde] Setting TDEROOTHOME to /root/.trinity.
[starttde] XDG_DATA_DIRS: /opt/trinity/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop
[starttde] TDEDIR: /opt/trinity
[starttde] TDEDIRS: 
Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0"
Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0"
Invalid MIT-MAGIC-COOKIE-1 keyxsetroot:  unable to open display ':0'
[starttde] Starting Trinity...
Invalid MIT-MAGIC-COOKIE-1 key[2047/04/20 13:31:05.603] kdetcompmgr: cannot connect to X server :0
[starttde] Trinity hardware control dbus daemon running.
Invalid MIT-MAGIC-COOKIE-1 key[2047/04/20 13:31:05.648] tdeinit_displayconfig: cannot connect to X server :0
Invalid MIT-MAGIC-COOKIE-1 key[2047/04/20 13:31:06.207] ksplash: cannot connect to X server :0
Invalid MIT-MAGIC-COOKIE-1 keyxprop:  unable to open display ':0'
[starttde] TDE_FULL_SESSION: true
[starttde] TDE_SESSION_UID: 1000
Invalid MIT-MAGIC-COOKIE-1 key[2047/04/20 13:31:07.644] tdelauncher: cannot connect to X server :0
[tdeinit] Communication error with launcher. Exiting!
[starttde] tdeinit started successfully.
Invalid MIT-MAGIC-COOKIE-1 key[2047/04/20 13:31:07.734] tdeinit_phase1: cannot connect to X server :0
[starttde] Shutting down Trinity...
[tdeinit wrapper] Warning: socket connection failed: : Connection refused
[tdeinit wrapper] Error: Can't contact tdeinit!
[starttde] Running Trinity shutdown scripts...
Invalid MIT-MAGIC-COOKIE-1 keyxprop:  unable to open display ':0'
[starttde] Trinity shutdown complete.

I have other desktop environments installed, because I was compelled to. But I never used them. TDM is set to be my default session.

I also tried backing up the /tmp directory so I could safely erase all inside it; willing to have all recreated and set in the next boot, but the issue persists. I tried editing MIT-MAGIC-COOKIE file myself but, unfortunatelly, they are binary type.

The syslog says TDM got segmentation fault, xsession-errors says it couldn't open display.

Is it a "permission" issue or a "memory access" issue?

[mrmazda]

You may wish to consult the TDE mailing lists. I don't remember seeing any complaints there from Buster users lately, but I suspect there aren't any 14.0.13 users left there. 14.1.2 is due before 1 May. If I were you, I would get upgraded to 14.1.1 now, and in a few days to 14.1.2. All my Debian installations are @14.1.1, Buster included, & anxiously awaiting 14.1.2.

ircs://libera.chat/trinity-desktop is another place where TDE users help each other.

Does /var/log/tdm.log have anything useful to add? /var/log/Xorg.0.log?

If you create a new user login, does trying it produce the same failure?