[Tutorial] Install the Trinity Desktop Environment

FAQ and Tutorials
1

Introduction

Trinity Desktop Environment (TDE) is a continuation of KDE 3.

Imgur

From Wikipedia:

The Trinity Desktop Environment (TDE) is a complete software desktop environment designed for Linux and Unix-like operating systems, intended for computer users preferring a traditional desktop model, and is free/libre software. Born as a fork of KDE 3.5 back in 2010, it was originally created by Timothy Pearson, who had coordinated Kubuntu remixes featuring KDE 3.5 after Kubuntu switched to KDE Plasma 4.

TDE is now a fully independent project with its own personality and development team, available for various Linux distros, BSD and DilOS. It is currently led by Slávek Banko.


Install TDE


1. Add Key from Trinity Developers

1a) Import the key:
sudo pacman-key --recv-keys D6D6FAA25E9A3E4ECD9FBDBEC93AF1698685AD8B

1b) It is recommended to verify the fingerprint:
pacman-key --finger D6D6FAA25E9A3E4ECD9FBDBEC93AF1698685AD8B

1c) Locally sign the imported key:
sudo pacman-key --lsign-key D6D6FAA25E9A3E4ECD9FBDBEC93AF1698685AD8B



2. Add TDE Repository

2a) Edit /etc/pacman.conf and add the following lines (likely at the bottom):
[trinity]
Server = https://mirror.ppa.trinitydesktop.org/trinity/archlinux/$arch

2b) Sync and Refresh databases:
sudo pacman -Syyu



3. Install Trinity Desktop packages

3a) The tde-meta package provides all trinity packages:
sudo pacman -Syu tde-meta
OR a smaller selection can be had with tde-tdebase package:
sudo pacman -Syu tde-tdebase
 
Note: The following groups exist:   [tde-core]  [tde-base]  [tde-libs]  [tde-extra]



4. Enable Trinity Display Manager (TDM) for Login
  1. Enable tdm.service:
    systemctl enable tdm.service

Conclusion

Thats it. You should now be able to use TDE after a restart.


More Information

Note

This is entirely untested by me. <3 cscs <3

Official Site

trinitydesktop.org

See Also

Trinity - Arch Wiki

2

I tried the guide from Trinity’s wiki in a VM a few days ago and it worked nicely.

The crucial difference from your guide is the keychain - it’s way longer. You sure your key is correct?

3

Its the “short key ID” .. you will notice the last 8 digits you reference match the 8 digits presented here.

$ gpg --keyserver hkp://keys.gnupg.net --search-keys D6D6FAA25E9A3E4ECD9FBDBEC93AF1698685AD8B
gpg: data source: http://185.125.188.26:11371
(1)     Trinity Desktop Environment Archive Signing Key
          4096 bit RSA key C93AF1698685AD8B, created: 2019-04-19
Keys 1-1 of 1 for "D6D6FAA25E9A3E4ECD9FBDBEC93AF1698685AD8B".  Enter number(s), N)ext, or Q)uit > Q

$ gpg --keyserver hkp://keys.gnupg.net --search-keys 8685AD8B
gpg: data source: http://185.125.188.26:11371
(1)     Trinity Desktop Environment Archive Signing Key
          4096 bit RSA key C93AF1698685AD8B, created: 2019-04-19
Keys 1-1 of 1 for "8685AD8B".  Enter number(s), N)ext, or Q)uit > Q

( You may notice the “long key ID” also match C93AF1698685AD8B - which is also just the last 16 digits of the fingerprint. )

This was initially written as it is simply because its closer to what Arch suggests, though they do so in yet another string;

But I see no reason why we could not use the full fingerprint in the guide here.

Edit.

And its done. The guide now uses the full fingerprint.