31 Oct
2021
31 Oct
'21
6:42 p.m.
Hello friends, I switched from FreeBSD back to Debian for several reasons:
* More software (not necessarily just Trinity), especially with flatpaks
* More documentation since I continued to have "unsolved mysteries" on FreeBSD
* Greater performance and hardware support
* GNU/Linux just as free as in freedom as FreeBSD, I was a bit one sided before
But I have an issue. I have installed most core components of Trinity (tdebase,
tdeaccessibility, tdegraphics etc.) but I always start in a tty when booting. I tried to
execute the starttde script but it doesnt work. Furthermore if I add it to .xinitrc and
run startx, it doesn't work. If I remove my home .xinitrc file and use startx, the
session will start but I can't use TDM at all.
Running the script directly is a lot more verbose, telling me that pretty much nothing can
connect to the X server. I have seen this talked about before in the ML but it seems like
they solved it. I used to use the preliminary testing branch and it worked but I decided
to go with stable this time and can't seem to get TDM to work at all. That pesky X
server.
31 Oct
31 Oct
6:56 p.m.
On Sun October 31 2021 11:42:06 Hunter Ellett via tde-users wrote:
But I have an issue. I have installed most core
components of Trinity
(tdebase, tdeaccessibility, tdegraphics etc.) but I always start in a tty
when booting. I tried to execute the starttde script but it doesnt work.
Furthermore if I add it to .xinitrc and run startx, it doesn't work. If I
remove my home .xinitrc file and use startx, the session will start but I
can't use TDM at all.
Running the script directly is a lot more verbose, telling me that pretty
much nothing can connect to the X server. I have seen this talked about
before in the ML but it seems like they solved it. I used to use the
preliminary testing branch and it worked but I decided to go with stable
this time and can't seem to get TDM to work at all. That pesky X server.
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?
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?
Maybe you just need to install tdm-trinity and reboot?
--Mike
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.
8:35 p.m.
UPDATE: I got it working! It turns out I needed to install the Xorg
metapackage, I was missing a few key things. I thought it installed as a
dependency alongside tdebase-trinity. Thanks
11:38 p.m.
said Hunter Ellett via tde-users:
| On Sunday 31 October 2021 04:01:25 pm Mike Bird wrote:
| > :-)
|
| Well, I spoke too soon.. Restarted and the same things happening. I
| guess it was a temporary solution.
Does ~/.xsession-errors cast any light on the problem?
--
dep
Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/
1 Nov
1 Nov
2:02 a.m.
On Sunday 31 October 2021 06:38:06 pm dep wrote:
Does ~/.xsession-errors cast any light on the problem?
It spits out the same thing that the typescript I pasted did with a bit more
information at the top. I attached it to keep this message from being too long
(and trimmed the file to whats TDE-related since it was huge).
On Sunday 31 October 2021 07:02:02 pm William Morder via tde-users wrote:
You said that if you use sysvinit, every Debian
package wants to uninstall
it; that's because Debian uses systemd. If you want sysvinit, rather than
systemd, then you must use Devuan or another non-systemd distro (e.g. MX
Linux, etc.). Devuan is nearly identical to Debian, and most packages are
interchangeable between them.
I am not saying that you ought to prefer one over the other. Others will
have their own preferences, too.
Yes, I have equal experience with Devuan. I've used both for quite some time
before FreeBSD. I chose to go with Debian since 1. the Devuan mirrors are
quite slow for me and 2. Debian is making moves towards init freedom:
https://wiki.debian.org/Init
Unfortunately, I followed these steps and sysvinit works but everything wants
to remove it. It doesn't look like there's any way to update-alternatives to
your init. I am not a fan of systemd myself but I started using Pipewire to
make Linux audio more bearable and it's a bit of a hassle without systemd for
now. Since I'm on Sid, if something changes I'll be the first to know. Maybe
sooner or later we'll see if Debian packages become more init-independent.
--
~ Hunter
4:34 a.m.
New subject: [OT] Debian and sysvinit
On Sun October 31 2021 19:02:19 Hunter Ellett via tde-users wrote:
Unfortunately, I followed these steps and sysvinit
works but everything
wants to remove it. It doesn't look like there's any way to
update-alternatives to your init. I am not a fan of systemd myself but I
started using Pipewire to make Linux audio more bearable and it's a bit of
a hassle without systemd for now. Since I'm on Sid, if something changes
I'll be the first to know. Maybe sooner or later we'll see if Debian
packages become more init-independent.
Hi Hunter,
I'm running Debian Bullseye with sysvinit on servers, workstations,
laptops, and VPSs with no problems. The only desktop we use is TDE
but we do also run a few Gnome applications under TDE.
Bullseye is better than Buster where I did have to use some old
Stretch init scripts to make things work.
What is conflicting with sysvinit on your system?
--Mike
7:25 a.m.
New subject: [OT] Debian and sysvinit
On October 31, 2021 11:34:52 PM CDT, Mike Bird <mgb-trinity(a)yosemite.net> wrote:
What is conflicting with sysvinit on your system?
Synaptic and LibreWolf (from a remote repo) that I remember off-hand. At that point I
migrated to Devuan by changing the mirrors and upgrading so that I could test these
applications and they installed afterwards with no need to remove sysvinit. Also I read
that pipewire-pulse uses systemd-oriented scripts that prevent it from working.
I had installed Debian once which is when I tried to use sysvinit, then installed it again
without later that day.
12:02 a.m.
On Sunday 31 October 2021 15:31:48 Hunter Ellett via tde-users wrote:
On Sunday 31 October 2021 04:01:25 pm Mike Bird
wrote:
You said that if you use sysvinit, every Debian package wants to uninstall it;
that's because Debian uses systemd. If you want sysvinit, rather than
systemd, then you must use Devuan or another non-systemd distro (e.g. MX
Linux, etc.). Devuan is nearly identical to Debian, and most packages are
interchangeable between them.
I am not saying that you ought to prefer one over the other. Others will have
their own preferences, too.
On an older machine -- or for old farts who want to stick with what they
know -- Devuan may be the better choice.
Bill
:-)
Well, I spoke too soon.. Restarted and the same things happening. I guess
it was a temporary solution.
909
days inactive
910
days old
10 comments
4 participants
participants (4)
-
dep -
Hunter Ellett -
Mike Bird -
William Morder