tde-users

users@trinitydesktop.org

4426 discussions

Various bug reports
by raine263＠proton.me 02 Jun '25

02 Jun '25

Hi, Apologies if this is the wrong place to submit bugs. I initial tried reporting bugs via the Bugs link on the webpage, https://mirror.git.trinitydesktop.org/gitea/issues, but it requires a login, and doesn't give an option to create a new account. I'm on Arch Linux, and after using Trinity for a few days, I noticed a few issues: 1. Dolphin is lacking the option to have a common display for all directories 2. Konqueror: maximum thumbnail limit of 100MB is to small by modern standards. I have video files that are measured in 10s of GBs for example... 3. Konqueror/Dolphin: thumbnails for basically all modern video files (example: mkv h265) are not generated. Would be nice to have a modern ffmpeg backend. 4. Thumbnails for JPEG XL and AVIF images are not generated. Similarly, they cannot be viewed at all. 5. Switching to another virtual terminal session (like a Plasma 6 session running for another user) and then switching back to the TDE session results in black screen, with only the mouse cursor visible. (Using SDDM.)

2 1

Various bug reports
by raine263＠proton.me 02 Jun '25

02 Jun '25

2 2

TDE Environment Variables in Debian/Devuan
by Darrell Anderson 28 May '25

28 May '25

I am a Slackware user. I have a Devuan VM, primarily to observe TDE differences with Slackware and to test TDE interaction with other desktop environments (DEs). In the VM when I log into a DE other than TDE, such as KDE, Cinnamon, MATE, Xfce, etc., none of the TDE packages populate the respective DE panel menu. The reason is that none of the environment variables are set to find TDE software installed to the non standard /opt/trinity directory. Variables such as $PATH, $PKG_CONFIG_PATH, and $TDEDIR, $TDEHOME, etc. In Slackware I configure some /etc/profile.d scripts to modify these env. variables in a manner similar to starttde, but only if the user elects to include TDE variables in the environment. For you Debian users, is there an "adopted" TDE approach to allow a user to easily configure the environment variables? Thanks. :)

1 0

New Slackware Build Environment
by Darrell Anderson 26 May '25

26 May '25

Ladies and gentlemen, hobos and tramps, flies and mosquitoes, and bald-headed ants, For some time I have been creating a set of TDE build scripts for Slackware. Like many such projects, this started as a way to scratch my own itch. The scripts are written in the spirit and style of stock Slackware, SBo, AlienBOB, and Salix build scripts. On both 64-bit and 32-bit Slackware 15.0 I am able to compile 163 of 179 R14.1.4 packages. Spot tests on the desktop shows most everything functions. I built most of R14.1.4 on Current 64-bit, but a few glitches remain. For vintage computer users and for fun, I built most of the R14.1.4 packages on 14.2 64-bit (requires some updated stock packages). Excluding tde-18n, which at the moment builds as a single package, the build time for the remaining 162 packages is about 2 to 2.5 hours in a VM on my 8 year old 4-core system with SATA III SSDs. A 32-bit VM runs a bit slower. A test run on a dual core with 4 GB RAM and using the SATA II SSD as working space rather than tmpfs required about 5.25 hours. The scripts will compile with debug symbols for those who want to help debug and troubleshoot. The scripts are flexible with many build options. For many Slackware users the script collection likely is complete. Sounds encouraging so many packages can be compiled, but there remain challenges beyond my skills and experience. Although good quality beta at this stage, minutia and hair balls remain. Time to let this child go and let more capable hands finish the scripts. Remaining needs: * Expertise to finish the language bindings scripts. * LDAP and (Heimdal) Kerberos expertise to finish related scripts. * Split the i18n packages into individual language packages. * Test and break the scripts (they work well here but who knows). * Find missing patches, fix nuances, etc. * Patch TDE cmake and automake files to improve Slackware support. * Usability testing to ensure packages compiled correctly. * Ensure debug symbols create useful back traces. Gory details are available in the script documentation. Yes, there is documentation as well as significant commentary in the scripts. I ask the following: * Consider the build environment to be quality beta, usable and fairly solid but incomplete. * Please inform me if the scripts are moved online to a centralized location. I am letting go of the project, but I'm curious to see how my baby grows up. * I have no intention of joining or creating accounts on git flub or any other such service. Doesn't interest me. If you move the scripts online in that manner I will help through email as best as I can when asked. * As best as I can I will reply to emails about what rope I was smoking when I conjured up certain code and functions. Please do not flood me with a multitude of questions in a single email. I'm an old man, sometimes a grumpy old man. One or two topics per mail please. * I am not paid tech support. I have taken the scripts as far as I can go. As best as I can I will help but from now on, you break you fix. * I am not tethered to a phone or the web. I check email but do not expect Pavlovian replies. * I accept that just about everybody has different perspectives and ideas how build scripts should function. My hope is my approach is good enough for others to finish and polish. I hope Slackers use the scripts at a personal level, but my long term goal always has been that the scripts are massaged to become part of the TDE packaging system. I want all interested Slackware TDE users to benefit. This move would provide a centralized set of scripts for all Slackware users, but would provide a way to allow Slackware users to download binary packages, much in the way of other third party repos like AlienBOB and Salix. Okay. Enough of the sales pitch. Here is a link to a 13.2 MB tar.gz of the script collection: https://www.remembertheusers.com/files/tde-slackware.tgz To use the build scripts, unpack the archive and read tde.GETSTARTED. To help resolve known issues read tde.FIXME. The script collection could be much smaller, but I included build script collections for two untested obtuse third-party packages for k3b and koffice. Statler and Waldorf commentary about my scripts or senility should be forwarded to /dev/null. Thank you Jim Diamond for your reviews, patience, and insights with the scripts. I learned a few things from you. Thank you for your attention. May we always see darkstar on our first boot. :-) D.A.

2 1

Problem when shutting down the computer
by ajh-valmer 26 May '25

26 May '25

Hello, Since I upgraded to the latest version of TDE, when I turn off my computer I often get this message : "Job -c scope / stop running (min sec ) /" Many times I have to wait a long time before the computer turns off. It's annoying when it's late and you want to sleep. Why this message when I shutdown the computer. Thank you , cheers. André

8 19

TDE and AD (samba) integration
by deloptes 24 May '25

24 May '25

Hi, I am trying to integrate TDE with Active Directory (SAMBA4). The system is fine, I can login to it on the console or via SSH with the domain user, but in the TDM login manager it doesn't work. Does someone know what I have to do to integrate/configure, or it is not working? thanks

1 2

Kate won't remember syntax highlighting
by Darrell Anderson 18 May '25

18 May '25

For some time a quirk in Kate has been haunting me. Kate seems unable to remember my syntax highlighting selections. This happens with two different user accounts on two different computers. I have Kate configured to store meta data for 180 days. Browsing the meta data file finds all affected files are stored and the 'Highlighting=' key is correct. As soon as I launch Kate the highlighting is plain text and the meta data file 'Highlighting=' key is empty. Deleting the meta file and starting from scratch has no effect. I don't use KWrite and can't offer any related observations. Any ideas? Thanks. :)

2 4

kvirc FTBFS
by Darrell Anderson 11 May '25

11 May '25

I'm getting closer to being able to build all 170 TDE packages in Slackware 15.0. Up to 161 compiled. :) Using autogen.sh, attempting to compile kvirc fails: ### CONFIGURE ERROR: ### Can not find the tqt 3.x library file. ### Make sure that tqt is correctly installed on your system, ### and the tqt version is the one requested by this version of kvirc. ### (Usually a greater version is OK too) I don't know, every other package found tqt3. The autogen.sh seems to complete successfully although there are a boat load of warnings (warnings are not errors?). My configure options: ./configure \ --disable-rpath \ --prefix=$INSTALL_DIR \ --sysconfdir=$SYS_CONF_DIR \ --libdir=$LIBDIR \ --mandir=$MANDIR \ --with-qt-dir=$INSTALL_DIR \ --with-qt-includes=$INSTALL_DIR/include \ --with-qt-libraries=$INSTALL_DIR/lib$LIBDIRSUFFIX \ --enable-closure || exit 1 Thanks for any help. :)

3 2

bibletime FTBFS
by Darrell Anderson 10 May '25

10 May '25

I'm getting closer to being able to build all 170 TDE packages in Slackware 15.0. Up to 161 compiled. :) Using cmake, attempting to compile bibletime fails: /usr/bin/ld: backend/libbackend.a(cswordmoduleinfo.cpp.o): undefined reference to symbol '_Z16lucene_wcstoutf8PcPKwm' /usr/bin/ld: /usr/lib64/libclucene-shared.so.1: error adding symbols: DSO missing from command line The clucene 2.3.3.4 package is installed. /usr/lib64/libclucene-shared.so.1 is installed and sym linked to libclucene-shared.so.2.3.3.4. Thanks for any help. :)

2 1

ktorrent 14.1.4 FTBFS
by Darrell Anderson 09 May '25

09 May '25

I am compiling 14.1.4 packages for Slackware 15.0. ktorrent fails to build with the following fatal error: ktorrent-trinity-14.1.4/src/libktorrent/torrent/cachefile.cpp:44:10: fatal error: settings.h: No such file or directory I'm using cmake. Appreciate some help. Thanks.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users