At one time there were a few folks providing Trinity packages for Slackware. Do any of you folks have Trinity 3.5.13.2 packages available?

Or, build scripts for 3.5.13.1 or 3.5.13?

Thank you!

I finally got used to kde4 and I don't use any slow machines any more. Temporarily I don't have access to any slackware box, so can't really help you. Sorry. :-(

I resurrected my old build scripts and got 3.5.13.2 installed.

1 members found this post helpful.

Installation instructions on the Trinity site are for Slackware 12.2 and 13.1. I guess I'll send the developers a time machine for Christmas.

I still cannot get used to kde4 because they don't fix the unlock screen bug which affects everyday life. Another big problem for me is that konsole in kde4 doesn't handle the resize command (TIOCSWINSZ). The konsole in kde3 does.

The kde4 guys only focus on fantastic visual effects.

I have been using Trinity for a few years. I use the GIT branch and have been doing so for more than a year.

Occasionally I toggle to KDE 4.10.5, but 98% of my desktop time is Trinity. A while back I focused solely on using KDE4, but in the end the number of "paper cuts" in KDE4 outnumbered those in Trinity. If I ignore the akonadi fiasco, I have nothing against KDE4.

I'm active in the Trinity project and although the developers are few, I get to participate and have a say in how things go. That was my reason for requesting 3.5.13.2 packages for Slackware. Although I had built 3.5.13 packages, I never built packages for 3.5.13.1 or 3.5.13.2, having moved from 3.5.13 to GIT. I wanted the 3.5.13.2 packages to perform some comparative testing against various features and bugs in the GIT branch. I was looking for an easy way out by requesting packages. Took me a while to resurrect my old build scripts, but that is now out of the way and I have 3.5.13.2 packages.

No sales pitch here, but if you haven't tried Trinity in a while you might enjoy seeing how stable and snappy the desktop is. No akonadi either.

Does Trinity build on Slackware 14.0 and/or 14.1?

Yes to 14.0 because that is what I use. I have been using Trinity GIT on Slackware 14.0 since February 2013. I'm building a fresh package set as I write.

Recently for some testing purposes I built Trinity GIT in 13.1. I tried hard but Trinity GIT won't build in 13.0 or 12.2. We discovered cmake, udev, and xorg limitations with those older Slackware releases. So 13.1 is the minimum for GIT.

I don't know about 14.1. These days I tend not to update Slackware in any hurry, but I have on my to-do list to create 14.1 parition and test Trinity. I won't move to 14.1 unless Trinity is functional.

I'm optimistic that Trinity builds on 14.1 because there are Trinity team members who use bleeding edge distros, such as Arch, Mandriva, and Fedora. Thus they already have discovered and patched build issues from the bleeding edge versions of software, such as gcc, libpng, etc.

I don't have build scripts for general consumption. My build scripts are complicated to cover a variety of build options because I am one of the main testers for Trinity. I pretty much only build from GIT, which I keep synced locally, and not from tarballs. Nobody I know is hosting tarball snapshots from GIT --- although there are scripts in the GIT tree for creating tarballs from GIT:

http://git.trinitydesktop.org/cgit/scripts/tree

I have wanted for a while to create basic tarball build scripts but I just never find the time. A nice set of scripts would look for local tarballs or allow the user to create tarballs from GIT.

Edit: I use Trinity GIT in Slackware 14.0 in all of my systems here, which includes my primary desktop, a laptop, my HTPC, a VM, --- and even my PI and PII, the latter two of which I maintain only to test my sanity.

Like you, I build from GIT sources (most recently from the 20131111 update). Indeed, it is very snappy and integrates with KDE4 well. The one and only problem I have is with the dict panel applet, with its segfaulting when doing a word search. Since I don't use it a whole lot, I haven't dug deeper into why.

Please provide me the steps to duplicate (I don't use).

I'll file a bug report if I can duplicate the problem.

1). Select "Add to Panel".

2). In the search input field, type "dict" to locate the dictionary.

3). Add the applet to the panel. So far, so good with no errors.

4). In the "kdict" applet, type in a word to define and then press enter. Immediate segfault.

This is the only applet that I've encountered that fails. I haven't tried to debug it or even look at a stacktrace since I rarely use the applet nowadays. Klipper and Kmix, which I use frequently, behave well. Still in my otherwise thorough exploration of trinity, it's the only flaw I've encountered.

One thing that may be germane is that I build with "-O2 -march=native" on this P8Z77-V LX (Quad-Core Hyper-Threaded Intel(R) Core(TM) i7-3770K @ 3.50GHz) box. Those CXXFLAGS/CFLAGS may be too aggressive.

Okay, thank you. Duplicated! No useful backtace either. Bug report 1748 filed.

Thanks so much...I was just about to compile with "-O0 -ggdb" and explore it further thinking it was unique to my environment. Good to know it's not just me!

Good to hear that. I didn't think so before due to the lack of HAL in slackware 14.1.

Trinity GIT has its own hardware detection support. Probably still has a few kinks, but I have no problems with optical disks or flash drives.