31 Oct
2021
31 Oct
'21
8:28 p.m.
On Sunday 31 October 2021 01:56:13 pm Mike Bird wrote:
Hi Hunter,
We're going to need a lot more details. Systemd or sysvinit or something
else? What exactly are you doing and what exactly errors result?
Its systemd. Any time that I use sysvinit on Debian every package wants to
remove it so I didn't bother. In the tty, I run /opt/trinity/bin/starttde
(since this script is not in PATH) which precisely results in the following:
[starttde] Starting starttde.
[starttde] This script is /opt/trinity/bin/starttde
[starttde] TDE version is R14.0.11
[starttde] TDE base directory is /opt/trinity
xsetroot: unable to open display ''
[starttde] TDEHOME is not set.
[starttde] Set TDEHOME to /home/hunter/.trinity.
[starttde] Setting TDEROOTHOME to /root/.trinity.
[starttde]
XDG_DATA_DIRS:
/home/hunter/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/:/opt/trinity/share:/usr/local/share:/usr/share
[starttde] Clearing setting of font DPI value
xrdb: Can't open display ''
[starttde] TDEDIR: /opt/trinity
[starttde] TDEDIRS:
xset: unable to open display ""
xsetroot: unable to open display ''
[starttde] Starting Trinity...
[starttde] Trinity hardware control dbus daemon running.
[2021/10/31 15:21:04.377] kdetcompmgr: cannot connect to X server
[2021/10/31 15:21:04.383] tdeinit_displayconfig: cannot connect to X server
[2021/10/31 15:21:04.391] ksplash: cannot connect to X server
xprop: unable to open display ''
[starttde] TDE_FULL_SESSION: true
[starttde] TDE_SESSION_UID: 1000
[tdeinit] Aborting. $DISPLAY is not set.
[starttde] tdeinit started successfully.
[2021/10/31 15:21:04.419] tdeinit_phase1: cannot connect to X server
ERROR: Couldn't attach to DCOP server!
[starttde] Shutting down Trinity...
[tdeinit wrapper] Warning: socket connection failed: : No such file or
directory
[tdeinit wrapper] Error: Can't contact tdeinit!
[starttde] Running Trinity shutdown scripts...
xprop: unable to open display ''
[starttde] Trinity shutdown complete.
You're a lot less likely to encounter problems if
you go with the flow.
All Debian packages are designed to start their services when installed
so how are you preventing TDM from starting automatically, and why?
I haven't disabled anything. In fact, "systemctl list-units" shows that the
tdm.service is running. I didn't do anything finicky but choose not to
install a desktop environment in the installer so I could get TDE, add the
Trinity repos, install the stable builds along with pipewire and firmware
that I need and this is how it was out of the box.
Maybe you just need to install tdm-trinity and reboot?
I have tdm-trinity installed.