tde-devels

devels@trinitydesktop.org

3803 discussions

New Slackware Build Environment
by Darrell Anderson 28 May '25

28 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

TDE 14.1.5
by Darrell Anderson 23 May '25

23 May '25

Will the dbus-tqt and tqtinterface packages be removed in 14.1.5? If yes, what do packagers need to know? Thanks.

2 2

Buttons in panels
by deloptes 21 May '25

21 May '25

Hi, I have a question for you more knowledgable. Since I installed (a self compiled) latest TDE few weeks ago, I observe very strange behavior of buttons in the panel. I have there many buttons and with most of them everything is fine. In fact it was fine with all of them for the past 20y. Since last upgrade if I click Signal or Teams-For-Linux buttons the applications do not start. Same applications start only from the console. How can I debug and where to look? I attach screenshots of the two configurations. thanks in advance -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

3 5

WTF is this in the wiki?
by Darrell Anderson 14 May '25

14 May '25

https://wiki.trinitydesktop.org/Over_40_Singles_Profile_Pictures:_7_Blunder…

3 3

Re: AC attached but battery symbol
by deloptes 13 May '25

13 May '25

Ilya Dogolazky via tde-devels wrote: > If some more info is needed I can of course provide it. I don't know, but it could be also a BIOS thing. IF not check dmesg or syslog regarding issues -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

1 0

Re: AC attached but battery symbol
by deloptes 13 May '25

13 May '25

Ilya Dogolazky via tde-devels wrote: > all the CPU are tacted by roughly 1000 Mhz which is > clearly not the max value (Intel page [1] says 4800 / 3500 MHz). why do you expect to see something more? what shows your /sys - this is what you also see in the UI $ cat /sys/devices/system/cpu/cpu*/cpufreq/*freq 3400000 1600000 2061434 3400000 1600000 3400000 1600000 1896795 3400000 1600000 3400000 1600000 2181524 3400000 1600000 3400000 1600000 2186013 3400000 1600000 You can usually limit the power or it is done by the policy and scheme you are using. If you use in kernel user space, it will give the OS the opportunity to control the policy by some software. There are also tools to set the policy in command line BR -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

1 0

AC attached but battery symbol
by Ilya Dogolazky 13 May '25

13 May '25

Hello ! Usually my laptop is on power cable, but every time I disconnect it and/or attach it back, the TDE power programs go to crazy mode (sometimes even eating 100% CPU, but not today). Today it was a bit different kind of crazy, the cable is connected and you can see the following on the screenshot: 1) Battery symbol in the tray (WRONG) 2) Battery symbol in «tdepowersave info» (WRONG) 3) AC PLUGGED IN bullet in «tdepowersave info» (RIGHT) 4) `acpitool -B` output in XTERM My experience says, tde powersave was never working on any of my laptops for many years. But maybe the reason ist that I only use Thinkpad ones, can it be? The current laptop is generation 10 (I guess, 10 but maybe 11, from the year 2022) X1 carbon. If someone could reproduce it somehow that would be great, but I don't know how to do it. Today it was like this: 1) Cable is attached, everything is fine (yesterday) 2) Go to sleep: «echo mem > /sys/power/state» 3) Later removed cable to charge my phone with it (laptop still sleeping in mem power state) 4) In the morning opening the lid to wake it up (working now) 5) Later: remember to attach cable (usually I do it before waking it up, but not today) 6) I see the battery symbol and make this screenshot 7) Going to sleep / awayking or cable connect/disconnect don't change the icon. If some more info is needed I can of course provide it. Cheers! -- Ilya D. --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

1 1

Re: bibletime FTBFS
by Darrell Anderson 12 May '25

12 May '25

On 5/11/25 7:34 PM, Calvin wrote: > All my testing here indicates bibletime does not function any more due to some rendering issues. the project has a mature, non KDE upstream project that continues to maintain and improve the project independently for 15 years. I think we should discontinue supporting KDE3 bibletime and let people use the upstream one. I am inclined to agree, but could the same be said about several TDE packages? Such as kmymoney, tellico, digikam, krusader, dolphin, koffice (calligra), chalk (krita).... I would not surprised if some packages such as bibletime, which I never have used, are getting crusty. Anyway, for now all I am trying to accomplish is getting all 179 packages to compile on Slackware. :)

2 2

bibletime 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 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 2

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. :)

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels