Trinity Desktop Environment version 3.5.12 has been released! This version provides significant enhancements to areas such as Personal Information Management (PIM), GTK application support, stability, and usability.

Trinity 3.5.12 is available for Slackware 12.2.

Improvements over KDE 3.5.12 are many. Detailed lists of improvements available here: Release Notes for Trinity v3.5.11 and Release Notes for Trinity v3.5.12.

The latest release is faster, more secure, and more feature rich than 3.5.10. Trinity incorporates the latest patches from multiple KDE enhancement projects, such as OpenSUSE, Chakra, Slackware, and Ubuntu.

Slackware 12.2 binary packages are available at Trinity Desktop Environment.

A complete Slackware 12.2 build script environment and documentation are available at KDE 3.5.x for Slackware.

As KDE 3.5.10 was last supported in Slackware 12.2, that release was a natural starting point for building and testing Trinity 3.5.12. The build scripts support patching KDE 3.5.10 as well as building Trinity from source tarballs and SVN. Starting with 12.2 serves as a stable cornerstone toward supporting post Slackware 12.2 releases. Packages for those releases are not yet available, but plans include Slackware 13.0, 13.1, and Current. The build script environment has been developed with that goal in mind.

If you are a 12.2 user, please feel welcome to download the final binary packages. Do notice that the packages for 12.2 do not presume KDE 4 or QT 4 are installed because those packages were not installed in 12.2. That is, the packages install in /usr rather than /opt and are considered a direct update/replacement to KDE 3.5.10.

The build script environment supports rebuilding the 12.2 packages using an alternate install location. Packages for subsequent Slackware releases will install Trinity along side KDE 4 and QT 4. The build script environment already supports this.

If you are a Slackware 13.0 or 13.1 user and enjoy the KDE 3.5 desktop, please feel welcome to help test and expand the build environment to support those releases.

If you use older hardware and miss KDE 3.5.10, then Trinity is a desktop environment option for you. Trinity is fully backward compatible with KDE 3.5.10 user profile directories and configuration files.

Enjoy!

Are we planning to get a version for Slack 64 in the future?

Hi,
I installed Trinity but for some reasons the KDE (Trinity?) menu is empty - there are no links to applications. I made the Trinity installation on a clear Slackware 12.2 that never before KDE was installed. What did I do wrong? Maybe I should at first install KDE 3.5.10 and after that make an upgrade with Trinity?

Thanks very much Woodsman! I am downloading the files as I write and will install and report any issues (if any) tomorrow. Thanks for helping keeping KDE 3.5.x alive.

The other things I mentioned are 'Empty windows'. Eg. when I tried to configure my desktop - to set wallpaper etc. opened an empty window. I am posting because I don't know what I should to expect. Should I be worried or simply wait when these problems will be fixed? KDE alive reminds to me the
KQ alive - the game I like very much. Of course many thank's for KDE 3.5.12.

Installed and running correctly there on 12.2 using your packages. So far, no issues like igadoter noticed.

igadotter, did you use Woodsman's packages or build using the scripts? Did you install everything?

Could it be the GTK-QT-engine? I experienced problems with that in the past(I haven't tried it with Trinity, though), so I have it disabled and will uninstall it later.

I experienced one isssue, Amarok was linked to libmp4v2.so.1 , which doesn't exist on my system, although I have libmp4, so I created a symlink to libmp4v2.so.0 and it runs fine. Which package supplies libmp4 on you system, Woodsman? My system is rather crufty and I haven't located whicch package supplies it yet.

This is great! I look forward to the planned releases for 13.1/current, but in the meantime has anyone tried these packages out on -current yet?

Just noticed another, more serious issue on my end. If I attempt to browse the web with Konqueror, I get this message:
Local web pages open OK as files, but not local servers like the CUPS web admin page, for example.

EDIT: I've located the package providing libmp4v2 on my system, it's faac-1.26-i486-1_SBo.tgz

EDIT 2: I've noticed that with Woodsman's packages at least some KDE programs are linked against libnvidia-tls.so.1 If I remember correctly, the proprietary Nividia video drivers replace some X11 and OpenGL libraries with their own versions. This might explain igadotor's problems if the packages were compiled on a system with the Nvidia drivers installed and he uses anothe graphics card.

As Woodsman says, for 13.1 or -current you will need to download the source and slackbuilds and build them yourself. Unfortunately, the already built packages will not work on -current, 13.0 or 13.1.

EDIT: I notice the version of ktorrent with Trinity is 2.2.6 The final version of ktorrent for KDE 3.5 is 2.2.8. Perhaps that could be included for the next release of Trinity

Thank Eternal_Newbie. I downloaded the binary packages again. I will reinstall Trinity. If you are right with those nvidia libraries there will be no choice only to compile from sources.

Aside from the (mostly expected) early troubles with packaging and unwanted dependencies [1], I have to give my kudos to this project. It's not something I'm personally interested in using, but I'm glad to see that there are still folks who care enough to keep the "old" kde going.

[1] I've been there - I remember my *early* days of distributing packages. Here's some unsolicited advice: virtual machines are your friends. If you don't have hardware capable of doing that well, then you'll have to create some dedicated partitions and build in chroot environments (or just boot into them first). You don't want to make a habit of distributing "dirty" packages.

OK, I've just experienced igadotor's problem, and I'm running the Nvidia drivers, so it's not caused by that.

The contents of the KDE menu disappeared except the launch progam, Control Center and Home entries, and the KDE control centre also appears empty. exiting KDE, renaming the ~/.kde3 (used by Trinity) and ~/.kde (just in case), ~/.config/menus/ and ~/.config/kde.org/ directories didn't help. It then just starts with default settings, without the welcome to KDE wizard, still no menu entries.

Most KDE programs start fine if started from launch program (or whatever it's called), a desktop shortcut or from a console window. KDE control centre and anything to do with it launches empty and without useful feedback.

I have no idea what causes this :/

EDIT: to be clear, this problem appeared out the blue, Trinity was working mostly OK before, apart from the issue of Konqueror not working as a web browser.

EDIT2: I may try building from the slackbuilds and reinstalling see if that helps.

Awesome! ;^)

I truely miss KDE 3.5.* since it was abandoned. Can we expect a binary release for Slackware 13.0/13.1/CURRENT in the near future?

It would be very nice to work on that desktop again.
I really tried, but still find the KDE 4.* series annoying :-/ (Would I be a programmer or a guru I would probably love it but not as the lunkhead I am

I agree. I really, really, like KDE 4. I think it is now (finally) better than KDE 3 and exceptionally usable.

But, I think it is important to have good choices and different options available.

My only question is whether Trinity will continue to be developed with bug fixes and new features, or if it will eventually hit a static (though still maintained) state where it gets updated as its dependencies change, but there's no innovation.

Thank's @Lufbery
I really, really don't like KDE 4 and I think that it is far away from being 'finall'.

Some guys work on substitutions for KDE 4 Gnome, Xfce, LXDE - some simple avoid to use it
at all. Trinity also can be a good substitution for KDE 4.