Difference between revisions of "Trinity"

From ArchWiki
Jump to: navigation, search
m (rm style note)
m (Refusing to give up the Trinity "Kicker" panel: style)
Line 78: Line 78:
Then from the command line, just type {{ic|startx}}. More about [[xinitrc]].
Then from the command line, just type {{ic|startx}}. More about [[xinitrc]].
== Refusing to give up the Trinity "Kicker" panel ==
== Trinity "Kicker" panel with other desktop environments ==
If you simply must have the Trinity "kicker" Desktop Panel and Applets while running Plasma5 or some other Desktop Environment, create this script and activate it. For Plasma5, use "System Settings -> Startup and Shutdown -> Autostart -> Add Script".
To use the Trinity "kicker" Desktop Panel and Applets with another desktop environment, create this script and make it [[executable]]. For Plasma5, use ''System Settings > Startup and Shutdown > Autostart > Add Script''.
/opt/trinity/bin/tdebuildsycoca --noincremental
/opt/trinity/bin/tdebuildsycoca --noincremental
# chmod 755 panelstart
== See also ==
== See also ==

Revision as of 12:51, 17 June 2017

The Trinity Desktop Environment (TDE) project is a fork of KDE 3.5 aiming to retain the traditional desktop style.

TDE still depends on an old version of Qt, which they now maintain themselves, since it is deprecated. The Trinity applications and applets should also work with other desktop environments.

Michael's PKGBUILD files

Michael's PKGBUILD repository contains PKGBUILD files for the ten required Trinity core packages described in How_to_Build_TDE_Core_Modules#Suggested_Build_Order, and also tdeaccessibility, tdebindings, and tdeutils.

Most PKGBUILDs seem to build fine except arts is a bit bugged (at least on VMWare). They seem to build successfully on a system with the plasma package group installed, despite the warning below about building with KDE4 being present. Binary packages are available for x86_64 at the moment, see Unofficial user repositories#trinity.

Build from source

As of July, 2015, there are no Arch Linux Trinity packages, so you will need to create your own. See Creating packages.

To download the R14 source tarballs, follow the Download Source Tarballs link near the bottom of the Trinity R14.0.0 Release page.

The sources are in a git repo. More info on cloning it is at their GIT information page.

The suggested build order is specified in the How to Build TDE page.

Building with Michael's PKGBUILD files

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements. See Help:Style for reference.Tango-edit-clear.png

Reason: All that matters is the order, the rest is trivial or available from the wiki (Discuss in Talk:Trinity#Trinity Build)
Note: See DeveloperWiki:Building in a Clean Chroot to build the packages in a chroot.

Build the packages in the following order, for example:

git clone https://github.com/michael-manley/Trinity_ArchLinux_PKGBUILD.git trinity
cd trinity/R14.0.3

for pkg in tqt3 tqtinterface arts dbus-tqt dbus-1-tqt tqca-tls libart-lgpl avahi-tqt tdelibs tdebase tdebindings tdeaccessibility tdeutils; do
  cd "$dir"/tde-"$pkg"
  makepkg -Lsci

In TDE R14.0.3, the tdebindings package will not build with the current ruby 2.3 package installed on the system, or even with the ruby2.2AUR package, despite the R14.0.3 Release Notes claim to have "Added ruby 2.2 support". In particular tdebindings/qtruby/rubylib/qtruby/Qt.cpp seems to not be compatible with either package. Remove the ruby package while building tdebindings and re-install afterwards.

Then also, consider your preference for path ordering, whether /opt/trinity/bin should come before or after /usr/bin. This will give priority to one or the other of the KDE applications available through both Trinity and KDE/Plasma, if KDE/Plasma is also installed. The PATH environment variable may need to be modified in ~/.bash_profile and/or /etc/profile.d/trinity.sh.

Warning: If Trinity is installed alongside another Qt-based Desktop Environment, such as LXQt or KDE, then move, modify, or in some way disable /etc/profile.d/tqt3.sh and /etc/profile.d/trinity.sh. Otherwise the alternative Desktop will fail horribly when the "QT" and "XDG" environment variables are redefined in these files!

Both these files can be selectively enabled by wrapping their content with:

if ps -C starttde,starttrinity &>/dev/null ;then

Start and configuration

After a successful install of TDE, the tdm desktop manager can be used to start TDE (and all other desktops) in the same manner kdm is used to start KDE Plasma. The init script for the display manager has been renamed from kdm to tdm to avoid conflicts. TDE includes a tdm.service file allowing systemd to start tdm at boot. TDE can also be started from the command line by including the path to starttde in your ~/.xinitrc. Either way launching tdm or TDE is straightforward.

Enable tdm.service in systemd to start tdm at boot

If systemd is configured to boot the default multi-user.target (default), all that is required is to configure tdm to start at boot is to enable tdm.service.

If you encounter any problem, the default.target may have manually configured. See Display manager#Loading the display manager for resolution.

Configure to work with startx

Trinity provides a normal starttde. If you've followed the Arch packaging guidelines, it will be in /usr/bin. The easiest way to start Trinity is to simply add starttde at the end of ~/.xinitrc. If you do not presently have ~/.xinitrc, then simply copy it from /etc/skel or create it with the following entry:

exec starttde

Then from the command line, just type startx. More about xinitrc.

Trinity "Kicker" panel with other desktop environments

To use the Trinity "kicker" Desktop Panel and Applets with another desktop environment, create this script and make it executable. For Plasma5, use System Settings > Startup and Shutdown > Autostart > Add Script.

/opt/trinity/bin/tdebuildsycoca --noincremental

See also