tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

TDE Crash Report dialog
by J Leslie Turriff 28 Apr '24

28 Apr '24

Occasionally a TDE component crashes and produces a dialog for reporting the crash. If I fill in my email address and a description, then send it off, where does it go? Is it integrated with the TDE bug reporting system? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 (x86_64) Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.1 tde-config: 1.0

1 0

[François] Fedora 40 released Tuesday 23 April
by Felix Miata 25 Apr '24

25 Apr '24

f40 is absent from http://tde-mirror.yosemite.net/trinity/rpm/ and http://archive.trinitydesktop.net/trinity/rpm/ -- 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

2 1

Re: [François] Cant install Trinity in Tumbleweed
by Felix Miata 14 Mar '24

14 Mar '24

Felix Miata composed on 2024-02-20 13:54 (UTC-0500): > jacobheinrich--- composed on 2024-02-20 17:02 (UTC): >> If it helps any, I was able to find that package, but now I am stuck at 'libOpenEXR-3.1.so.30()(64bit)' > It often happens that TW rolls a version forward while some TDE package requires > a specific version rather than some minimum version of that package. In order to > move installation along I usually choose to break anything that requires some > obsolete version, and report to devels(a)trinitydesktop.org so that François can be > aware of the conflict in his build scheduling. > In checking, I see the cached libOpenEXR package version is > -rw-r--r-- 1 805339 Feb 4 21:04 /pub/zyp/OSS/x86_64/libOpenEXR-3_1-30-3.1.11-1.3.x86_64.rpm > while an installed as of a month ago looks identical except for timestamps: > lrwxrwxrwx 1 25 Oct 9 05:28 libOpenEXR-3_1.so.30 -> libOpenEXR-3_1.so.30.11.1 > -rwxr-xr-x 1 3193104 Oct 9 05:28 libOpenEXR-3_1.so.30.11.1 > Contained lib in the rpm has the same byte size. The version did get a bump in the last TW release to reach the mirrors: # ls -gG libOpenEXR* -rw-r--r-- 1 805339 Feb 4 21:04 libOpenEXR-3_1-30-3.1.11-1.3.x86_64.rpm -rw-r--r-- 1 818108 Feb 20 18:49 libOpenEXR-3_2-31-3.2.2-1.1.x86_64.rpm -rw-r--r-- 1 510931 Feb 11 18:44 libOpenEXRCore-3_1-30-3.1.11-1.3.x86_64.rpm -rw-r--r-- 1 512218 Feb 20 18:49 libOpenEXRCore-3_2-31-3.2.2-1.1.x86_64.rpm -rw-r--r-- 1 81960 Feb 11 18:44 libOpenEXRUtil-3_1-30-3.1.11-1.3.x86_64.rpm # -- 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

2 2

Living in /opt
by Darrell Anderson 09 Mar '24

09 Mar '24

Are there plans to get TDE out of /opt and back into /usr? The topic was discussed a decade ago: https://bugs.trinitydesktop.org/show_bug.cgi?id=1934 For the past year or so that I have tried to return to TDE, I keep running into nuance issues. Things that motivate me to avoid TDE. Most of these speed bumps are caused by environment variables, mostly XDG related. I remember at the time everybody working on starttde trying to anticipate the many ways living in /opt could break and to avoid conflicts with KDE. My guess is many TDE users do not see these issues because they do not have a multi-user system with multiple desktop environments installed. Likely many to most TDE users are like other DE users -- just stick to familiar territory and ignore other DEs and potential conflicts. I think the easiest approach is renaming binaries with a tde- prefix. The MATE folks did this many years ago and continue the convention. I do not have a full TDE install, but on my system I found 30 files in /opt/trinity/bin that have the same file name in KDE. I know there are more because, for example, I do not have tdegames installed. Anyway, just curious, nothing else. Thanks.

2 1

Can't build tqt3
by darrella＠clovermail.net 28 Feb '24

28 Feb '24

I am unable to compile tqt3 on Slackware 15.0 64-bit. The build always fails with: /usr/bin/ld: cannot find -lpng Yesterday I thought I resolved the problem by disabling gcc visibility. Today that trick is futile. libpng-1.6.37 is installed. Any ideas?

3 2

OpenSuse TW: nothing proves 'libtiff.so.5()(64-bit)' needed
by jacobheinrich＠hotmail.com 28 Feb '24

28 Feb '24

I think something in the new compile of TW broke the dependency 'libtiff.so.5()(64-bit)". Did a zypper refresh already to make sure my repos were up to date.

2 1

Ray-V Slackware Build Scripts
by darrella＠clovermail.net 28 Feb '24

28 Feb '24

Some Slackware related build script observations that hopefully reach Ray-V. Some time ago I used your build scripts with the R14.0.12 release. Recently I used them with R14.1.1. * While git is popular among many computer people, some folks are not familiar. There are no instructions in the beginning of the README file how to download the zip file that creates the build environment. Selecting the little green 'Code' drop-down widget in the upper right of the web page might seem obvious to git users but not so straightforward to other folks. * Some mention in the README would be helpful that the zip file creates the expected build environment. * Some mention might be helpful that the source tarballs will need at least 630 MB or so of disk space. More space is needed if adding packages not directly supported by the default build environment. * A note would be helpful about how much build environment space is needed. The default is to build and store in /tmp yet many people now use tmpfs. My first pass at building the packages halted because I chose not to delete temporary files and soon filled my /tmp using tmpfs. I chose not to delete anything because I wanted to study the environment and copy the packages to a local repo. Perhaps mention that for tmpfs users the TMP environment variable needs to be changed or the parent BUILD-TDE.sh script needs to be edited. * A related note would be helpful that building koffice requires about 2.5 GB of temporary storage space. * I'm not an original Slacker from 1993, but I have been using Slackware since 2001. In those years I do not recall seeing a package touch the stock /etc/profile or the root user's ~/.bashrc. Likewise with modifying stock /etc/profile.d scripts. Unorthodox for sure and unsettling to us old farts. Traditionally such changes are added with new /etc/profile.d scripts specific to the package. * The build scripts provide users a nice way to download source files. The file names of those sources are not the same as the parent sources provided at the TDE mirrors. Seems incidental but I had already manually downloaded and untarred the TDE 'R14.1.1-complete.tar' source tarball. I got confused why the build script was still downloading source files. I am one of those unfortunate folks who still has a slow internet connection with monthly caps. I resolved the problem for myself but why the source files need to be renamed seems confusing. * Mentioned in the TDE wiki and SlackBuild README is the need for a special TDE related cmake file. The build script downloads this source file, but the parent TDE 'R14.1.1-complete.tar' source tarball seems to be missing that special tarball. This information probably should be forwarded to whomever automates building the parent tarballs. * My first run building tqt3 failed with a gcc error not finding -lpng. The solution was to toggle off the visibility setting in the parent build script. Perhaps this visibility option could be better explained. * The inline EOF patching is unorthodox from Slackware tradition. Stock and SBo build scripts have followed the same template for many years. The template method is to merge separate patch files. The EOF method is interesting but clunky, requiring more effort for a person who wants to fine tune a local build environment or add local patches. * Likewise with the unorthodox EOF way of creating the package 'slack-desc' file. * As far as I can see there is no support to include debug symbols. This long has been a shortfall of Slackware packaging. Without symbol support, users struggle to post helpful crash reports. Perhaps the build scripts could be tuned to allow keeping the debug symbols with the usual disclaimer that doing so will create larger packages. * Perhaps consider a parent build script question to build only core packages. When the build list dialog appears, all packages up to tdebase will be preselected but none others. This could be handy for people who tinker a lot. I'm not frothing about any so-called 'Slackware way' or demanding anything, but I have been building Slackware and SBo packages for many years. Also long ago I was part of the TDE team. I have ample experience to make all of these changes for myself, but these unorthodox approaches tend to be confusing. These are your build scripts, but I hope this information helps. Thanks for the build scripts.

1 0

cannot install to Fedora 39 absent --nogpgcheck
by Felix Miata 23 Feb '24

23 Feb '24

In Fedora 39, --nogpgcheck dnf option is required to initially install TDE. Without it, curl error due to failure to read non-existent /etc/pki/rpm-gpg/trinity halts possibility to proceed with installation. Is this expected? https://wiki.trinitydesktop.org/Fedora_Trinity_Repository_Installation_Inst… makes no mention. -- 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

1 0

filecommander will not run
by Felix Miata 18 Feb '24

18 Feb '24

# fcl [2023/11/12 00:53:53.248] TQWidget: Cannot create a TQWidget outside of the main GUI thread (fcl:2764): GLib-GObject-CRITICAL **: 00:53:53.248: g_object_ref: assertion 'G_IS_OBJECT (object)' failed # This is from Bookworm, but same result from Trixie. Works as expected in IceWM session. <http://silk.apana.org.au/pub/fcl/nightly/filecommander_2.50.vgit-1828-buste…> http://silk.apana.org.au/fc2development.php -- 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

1 6

dnf system-upgrade of Fedora 39 to 40/Rawhide requires excluding *jasper*
by Felix Miata 05 Feb '24

05 Feb '24

In order to get system-upgrade to proceed, I had to include *jasper* in /etc/dnf/dnf.conf's exclude= line. I suppose an alternative could have been creating a file in /etc/dnf/protected.d/ that includes jasper and jasper-libs. F39 jasper is 3.0.6. F40 provides 4.1.0. -- 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

1 1

← Newer
1
...
9
10
11
12
13
14
15
...
381
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels