https://wiki.trinitydesktop.org/Fedora_Trinity_Repository_Installation_Instructions provides great instructions for installing TDE on a working Fedora 37 system. But the last section provides no help for starting TDE from a "run-level 3" system (multi-user, not graphical). The built-in startx command does not detect TDE. Or, more specifically, the /etc/sysconfig/desktop script. Of course, I can modify that script but I have no idea what to add to it. It would be nice if the TDE installation provided an updated version.
On Sun, 05 Mar 2023 16:34:12 -0800 Dave Close via tde-users users@trinitydesktop.org wrote:
https://wiki.trinitydesktop.org/Fedora_Trinity_Repository_Installation_Instructions provides great instructions for installing TDE on a working Fedora 37 system. But the last section provides no help for starting TDE from a "run-level 3" system (multi-user, not graphical). The built-in startx command does not detect TDE. Or, more specifically, the /etc/sysconfig/desktop script. Of course, I can modify that script but I have no idea what to add to it. It would be nice if the TDE installation provided an updated version.
You probably need to point something at the starttde script. My .xinitrc just contains
/usr/trinity/14/bin/starttde
and TDE starts reliably when I run startx. I have no idea what distro-specific wrinkles Fedora may have added, though (and the path to the script will probably be different for you).
E. Liddell
I wrote:
https://wiki.trinitydesktop.org/Fedora_Trinity_Repository_Installation_Instructions provides great instructions for installing TDE on a working Fedora 37 system. But the last section provides no help for starting TDE from a "run-level 3" system (multi-user, not graphical). The built-in startx command does not detect TDE. Or, more specifically, the /etc/sysconfig/desktop script. Of course, I can modify that script but I have no idea what to add to it. It would be nice if the TDE installation provided an updated version.
E. Liddell answered:
You probably need to point something at the starttde script. My .xinitrc just > contains
/usr/trinity/14/bin/starttde
and TDE starts reliably when I run startx.
Thank you. I modified the /etc/X11/Xclients script to include this and startx now works wonderfully for me. Sorry it took so long to say so -- stuff happens in life.
The /etc/sysconfig/desktop script on Fedora is an optional way to specify which of the possible installed DEs should be used. It really wasn't relevant to my question and I simply misspoke. However, I did need to set it to "TDE" to avoid starting Fedora's KDE which is also installed. My revised Xclients is available on request.
But having KDE 5 installed before installing TDE seems to resulted in some confusion. The DE startup splash screen, for example, says it is starting Plasma by KDE. Once started, it does appear to actually be TDE. But some parts of TDE don't work as expected. For example, the TDE Control Center doesn't start if selected from the start menu. Nothing at all happens. Starting kcontrol from a shell does start what appears to be the program but nothing in it works. On exit, the shell reports, "WARNING: No TDE menu group with X-TDE-BaseGroup=settings found | Defaulting to Settings/". I have installed all of TDE itself but none of its applications.
On 3/5/23 6:34 PM, Dave Close via tde-users wrote:
https://wiki.trinitydesktop.org/Fedora_Trinity_Repository_Installation_Instructions provides great instructions for installing TDE on a working Fedora 37 system. But the last section provides no help for starting TDE from a "run-level 3" system (multi-user, not graphical). The built-in startx command does not detect TDE. Or, more specifically, the /etc/sysconfig/desktop script. Of course, I can modify that script but I have no idea what to add to it. It would be nice if the TDE installation provided an updated version.
Hi Dave,
I do not use Fedora and have no idea what /etc/sysconfig/desktop is for.
I am a long time Slackware user and have launched X from the command line for more than 20 years.
The traditional way to launch X from the console is with /usr/bin/startx, which actually is a shell script. At the command prompt type startx and see what happens.
The startx script looks for a $HOME/.xinitrc and if not found looks for /etc/X11/xinit/xinitrc, which often is a sym link to another xinitrc file in the same directory. The sym link is considered the system "default" xinitrc.
If installed correctly, and I presume the Fedora packager has done so, then one of those two xinitrc scripts will contain the command to launch /opt/trinity/bin.
I hope that helps.
DA
Dave Close via tde-users composed on 2023-03-05 16:34 (UTC-0800):
https://wiki.trinitydesktop.org/Fedora_Trinity_Repository_Installation_Instructions provides great instructions for installing TDE on a working Fedora 37 system. But the last section provides no help for starting TDE from a "run-level 3" system (multi-user, not graphical). The built-in startx command does not detect TDE. Or, more specifically, the /etc/sysconfig/desktop script. Of course, I can modify that script but I have no idea what to add to it. It would be nice if the TDE installation provided an updated version.
I'd like to know too. IceWM won't start with startx either. There's a legacy support configuration option out there that needs to enable Xorg directly from startx, but I don't know how to locate it.
$ /usr/bin/startx /opt/trinity/bin/starttde /usr/bin/sh: /usr/bin/X: Permission denied xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error $ ll /usr/bin/Xorg /usr/bin/X lrwxrwxrwx 1 root root 4 Feb 6 20:10 /usr/bin/X -> Xorg -rws--x--x 1 root root 277 Feb 6 20:07 /usr/bin/Xorg # ← NOT default perms $ uname -r 6.1.14-200.fc37.x86_64 $ rpm -qa | grep Xorg xorg-x11-server-Xorg-1.20.14-18.fc37.x86_64 $ /usr/bin/startx /usr/bin/icewm <same sequence as above> $ ll /usr/bin/icewm -rwxr-xr-x 1 root root 1609488 Jan 24 05:52 /usr/bin/icewm $ fpaste /usr/bin/startx Uploading (7.4KiB)... https://paste.centos.org/view/a548eca0
Maybe Darrell can spot something in startx that's different from Slackware. According to a primary X maintainer for SUSE, startx has not been supported "since more than 2 decades"[1] (for a non-root user). It fails on openSUSE with same results as on Fedora, and IIRC, I've see somewhere in Fedora mailing lists and/or RedHat Bugzilla comments to same effect.
Recent openSUSE bug I reported for trouble getting a default X session to start, which I couldn't reproduce when using TDM/TDE, addressed by same maintainer: https://bugzilla.opensuse.org/show_bug.cgi?id=1208268
[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1208198#c23 (mere recent example, though oft repeated)
On Mon, 6 Mar 2023 00:10:42 -0500 Felix Miata via tde-users users@trinitydesktop.org wrote:
Maybe Darrell can spot something in startx that's different from Slackware. According to a primary X maintainer for SUSE, startx has not been supported "since more than 2 decades"[1] (for a non-root user). It fails on openSUSE with same results as on Fedora, and IIRC, I've see somewhere in Fedora mailing lists and/or RedHat Bugzilla comments to same effect.
Not Darrell, but after plugging your file into a diff alongside mine, the following jumps out at me:
(Yours)
if [ "$have_vtarg" = "no" -a x"$vtarg" != x ]; then serverargs="$serverargs $vtarg" # Fedora specific mod to make X run as non root export XORG_RUN_AS_USER_OK=1 fi
(Mine)
if [ "$have_vtarg" = "no"]; then serverargs="$serverargs $vtarg" fi
Mine also doesn't trap the KILL signal. There are several other differences that don't appear to be germane.
However, spelunking through the ebuild shows me that there is an actual build-time option to make an X server require a logind provider (either systemd or elogind) when running as nonroot. There's also an option to be used in combination with this to set a suid wrapper needed by some video modules.
If your copy was compiled with -Dsystemd_logind=true, you need a logind provider. If you're unlucky enough to need the suid wrapper, but your X was compiled with -Dsuid_wrapper=false, it's possible that there's nothing you can do to fix this.
E. Liddell