tde-devels

devels@trinitydesktop.org

11 participants
3800 discussions

Start a nNew thread

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

ktorrent 14.1.4 FTBFS
by Darrell Anderson 10 May '25

10 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.

3 3

TDE Packaging System
by Darrell Anderson 10 May '25

10 May '25

What are the requirements to submit a collection of distro build scripts to the TDE packaging system? Once the scripts are part of the packaging system, will prebuilt packages then be available to anybody for downloading and installing? Thanks.

2 2

Fwd: Re: KDE3 vs. TDE in openSUSE
by J Leslie Turriff 10 May '25

10 May '25

After reading this, I wonder if it is actually why TDE is not available in openSUSE's mainline repositories, or some other reason? Leslie ---------- Forwarded Message ---------- Subject: Re: KDE3 vs. TDE in openSUSE Date: 2025-05-09, 19:22:21 From: Felix Miata <mrmazda(a)earthlink.net> To: kde3(a)lists.opensuse.org Gianluca Interlandi composed on 2025-05-09 16:29 (UTC-0700): >> What justifies KDE3 keep-alive as mature as TDE has become, now 14.1.4, >> 15 years later? > KDE3 is still part of the official openSUSE repositories. Yes, but not really. KDE3 got its own repo too long ago to remember, so yes, available from openSUSE, but requires special effort to install differing little from installing TDE. > Do you think > there is or there will be a way to make TDE part of the openSUSE > repositories? In this way, TDE can be selected during an openSUSE > installation instead as doing it after everything is setup. I know that > the Trinity website recommends installing packages from packman and > switching vendor before installing TDE. Maybe this can be done also after > TDE is installed? I've been disabling Packman in recent months. With so few remaining patents applicable, I haven't had any need for it in some time. >> With Leap 16 abandoning the hardware that makes the two shine, is 15.6 >> support cessation time to retire the old codepath and name? > Can you please elaborate what you mean by this? Are you saying that TDE > will not "shine" in Leap 16? What I meant with "shine" was KDE3/TDE notable liveliness on old hardware compared to contemporary DEs like Gnome, XFCE and Plasma. KDE3 was fast on 32bit when 64bit was a new thing most had yet to acquire. Gianluca Interlandi composed on 2025-05-09 16:43 (UTC-0700): > Now I see what you mean. Leap 16 will require x86_64-v2. How do you check > for this? For example, on Intel Core 2 Duo I have the following flags: Core2Duo/Quad is v1, dead for 16.0, as are some early Core i3/i5/i7 varieties IIRC. The deal breaking marker flag is sse4_2 that is missing[1]. If the CPU is in a 775 or older motherboard socket, AFAICT it's v1. [1] https://en.opensuse.org/X86-64_microarchitecture_levels -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.4 tde-config: 1.0

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels