tde-users

users@trinitydesktop.org

21 participants
4329 discussions

Problem installing Trinity in Debian
by J Leslie Turriff 01 Jun '23

01 Jun '23

Hello, I bought a new laptop for my brother and I've installed Debian 11.7 on it (with the default Gnome DE), but when (installing from USB stick) I try to select a mirror to download packages I get this: | Jun 1 09:50:59 choose-mirror[31078]: WARNING **: mirror does not support the specified release (bullseye) This has happened with both http://deb.debian.org/ and http://ftp.us.debian.org/ (!) I also tried installing without using a mirror for additional packages, but then apt-get doesn't work because of missing configuration files. Help! :-) Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 (x86_64) Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.0 tde-config: 1.0

3 3

~/.xsessionrc: osd_clock is not showing up on display anymore
by Stefan Krusche 01 Jun '23

01 Jun '23

Good day! After a recent update (see below) starting 'osd_clock' in ~/.xsessionrc does not work properly anymore. Osd_clock is an on-screen clock which is projected to the root window and through all program windows (on top). My setup: I have 'osd_clock' started in ~/.xsessionrc like this: exec osd_clock -r -o 10 -s 0 -F '%A, %d.%m.%Y :: %R Uhr ·%S·' & On my system (devuan beowulf) ~/.xsessionrc is sourced by /etc/X11/Xsession.d/40x11-common_xsessionrc which is sourced by /etc/X11/Xsession which is sourced by /etc/trinity/tdm/Xsession. This used to work for years. Problem behaviour: --- When I now log in into TDM, osd_clock briefly appears and then vanishes just before TDM starts the X-session. --- After that osd_clock is a running process, but does not show up in the display. $ ps aux | grep osd_clock stekru 3788 0.0 0.0 96124 4000 ? Sl 09:45 0:00 osd_clock -r -o 10 -s 0 -F %A, %d.%m. %Y :: %R Uhr ·%S· --- Apparently osd_clock is running with no terminal (the "?"). A manually started osd_clock is running fine and shows up like this (second line): $ ps aux | grep osd_clock stekru 3788 0.0 0.0 96124 4000 ? Sl 09:45 0:00 osd_clock -r -o 10 -s 0 -F %A, %d.%m. %Y :: %R Uhr ·%S· stekru 7871 0.0 0.0 96128 4036 pts/3 Sl 10:52 0:00 osd_clock -r -o 10 -s 0 -F %A, %d.%m. %Y :: %R Uhr ·%S· --- Meanwhile I found a workaround: start osd_clock with option "-w 5" to wait five seconds before showing up. Why does osd_clock not "find" the terminal (pts/3) anymore? I have no idea how to debug this further. Any help is appreciated. --- Before this symptom appeared I had upgraded some TDE packages (from /var/log/apt/history.log, redacted for readability): Start-Date: 2023-05-30 22:10:13 Commandline: apt-get upgrade Upgrade: ark-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), dcoprss-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kappfinder-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kate-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kcalc-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kcharselect-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kcontrol-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kdesktop-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kdf-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kdict-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kedit-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kfind-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kfloppy-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kget-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kgpg-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), khelpcenter-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), khexedit-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kicker-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kjots-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), klaptopdaemon-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), klipper-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kmenuedit-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kmilo-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), knewsticker-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), konqueror-nsplugins-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), konqueror-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), konsole-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kopete-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kpager-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kpersonalizer-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kpf-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kppp-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), krdc-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), kregexpeditor-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), krfb-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), ksim-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), ksirc-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), ksmserver-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), ksplash-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), ksysguard-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), ksysguardd-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), ktimer-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), ktip-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), kwifimanager-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), libkonq4-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), librss1-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), libtdebluez-trinity:amd64 (4:14.2.0~pre19-0debian10.0.0+1, 4:14.2.0~pre20-0debian10.0.0+1), libtdeobex-trinity:amd64 (4:14.2.0~pre19-0debian10.0.0+1, 4:14.2.0~pre20-0debian10.0.0+1), libtqt3-integration-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), mx-packageinstaller:amd64 (23.5.02, 23.5.03), superkaramba-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), sysstat:amd64 (12.0.3-2+deb10u1, 12.0.3-2+deb10u2), tde-i18n-de-trinity:amd64 (4:14.2.0~pre29-0debian10.0.0+0, 4:14.2.0~pre46-0debian10.0.0+0), tde-i18n-engb-trinity:amd64 (4:14.2.0~pre29-0debian10.0.0+0, 4:14.2.0~pre46-0debian10.0.0+0), tde-i18n-ru-trinity:amd64 (4:14.2.0~pre29-0debian10.0.0+0, 4:14.2.0~pre46-0debian10.0.0+0), tdebase-data-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), tdebase-runtime-data-common-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), tdebase-tdeio-plugins-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1) tdebase-tdeio-smb-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), tdebase-trinity-bin:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), tdebase-trinity-doc-html:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), tdebase-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), tdebluez-trinity:amd64 (4:14.2.0~pre19-0debian10.0.0+1, 4:14.2.0~pre20-0debian10.0.0+1), tdednssd-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdefilereplace-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdelirc-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdenetwork-filesharing-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdenetwork-tdefile-plugins-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdenetwork-trinity-doc-html:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdenetwork-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdepasswd-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), tdeprint-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), tdessh-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdeutils-trinity-doc-html:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdeutils-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdewalletmanager-trinity:amd64 (4:14.1.0-0debian10.0.0+0, 4:14.2.0~pre1-0debian10.0.0+0), tdm-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), twin-trinity:amd64 (4:14.2.0~pre8-0debian10.0.0+1, 4:14.2.0~pre10-0debian10.0.0+1), End-Date: 2023-05-30 22:10:34

1 1

kontact burning CPU increases since last upgrade
by deloptes 31 May '23

31 May '23

Hi, I am using kontact for mail, calendar, contacts and news Since last upgrade I have to restart it regularly, because over time it burns more and more CPU. Does anyone has any idea how to find out what is going on? thanks BR

1 0

Complete breakage of KRFB and KRDC
by Roman Savochenko 26 May '23

26 May '23

Hi Tell me please, the moving of KRFB and KRDC to the standalone libvnc in 14.1.0, this is for complete breakage of KRFB and KRDC or I misunderstand something? :) KRFB is just dead cycling in some QObject destructor at any connection before the password transmission even. KRDC shows the remote screen, but it is hanging mostly, when there impossible to close the program, only kill. Whether I must downgrade the KRFB and KRDC code back to 14.0.13?

5 9

Folders with locale
by ajh-valmer 23 May '23

23 May '23

Hello, In my "/home/andre" I have these 3 folders : TÃ©lÃ©chargements Téléchargements Vid©lÃ©os Vidéos ModÃšles Modèles If I delete TÃ©lÃ©chargements, Vid©lÃ©os and ModÃšles, at the next boot, they are automatically recreated. How to avoid this recreation ? localectl status System Locale: LANG=fr_FR.UTF-8 VC Keymap: (unset) X11 Layout: fr X11 Model: pc105 X11 Variant: latin9 In console mode the accented characters cannot be displayed, as é, à, è, ù... Thanks, Cheers, André

6 11

fonts changed in Kmail message body
by William Morder 22 May '23

22 May '23

Okay so this is another kinda weird one. I have been sitting on it for a couple weeks, just to make sure it wasn't something stupid that I did myself, or something that could be easily corrected, or whatever. On the surface, it's just another one of those trivial annoyances that doesn't matter much in the big scheme of things. But I think it's a bug, or some kind of deeper issue. I have accordingly tried to include as much relevant information as possible. Please feel free to trim in the responses. When I upgraded my system, Kmail now will not display my chosen font for the message body. I tend to prefer a bookish font myself, but they don't always display. For web creation stuff, for example, its good to do a little research on web-safe fonts, which are supposed to display on any page on any machine, etc. But this is, again, my own machine, so if I can get it to work, then it should not matter to anybody else; it's not like I am forcing others to use desktop that looks exactly like mine. Now, what's peculiar about this is that it only seems to affect the message body of the emails that I have received (and may or may not be reading). As I compose this email - the very words that you are reading at this moment - the message body of my own draft looks right.* [* Please see attachments for proof by screenshots. You will note that I enclosed a couple older screenshots that I still had in that folder, plus a couple more recent ones. The more recent ones show how my Kmail behaves differently between the message body in the composer, where it uses my chosen font, and the message display, where it seems to be forcing some version of mono.] I did switch round, try out some other fonts, bookish or not-so-much, but the song remains the same: I still get stuck with a font that looks like some version of mono. Not that it's totally illegible, and probably wouldn't bother others, but I do really hate reading ugly fonts. I'll keep digging, but so far, but I have been digging now for a couple weeks, and nothing changes, no clues, no progress. Any help will be appreciated. Don't have the slightest inkling what caused it, as I have been using Kmail like this since it was KDE3, back in the antediluvian days of about 2006 or so. I *ever* haven't changed a thing except the display font for Kmail; and last time I changed that was about five years ago. Otherwise, things have worked pretty much the same since day one, across multiple machines, users, operating systems, upgrades, and everything else that has happened between then and now. Bill P.S. For the record, I am running Devuan Chimaera 4.x (whatever is the current upgrade version), kernel verion is 5.10.0-23-amd64, and my Trinity desktop is given as R14.1.1~[DEVELOPMENT]. (I copied this from the display page for Trinity Control Center.) My current sources list; just the main and preliminary stable builds. # Trinity - TDE deb http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x chimaera main deb http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x chimaera main deb-src http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x chimaera main deb-src http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x chimaera main # Trinity preliminary stable builds deb http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb chimaera deps-r14 main-r14 deb-src http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb chimaera deps-r14 main-r14

1 0

This error related to TDE?
by Michael 21 May '23

21 May '23

I'm not sure what part of gtk TDE does, but saw this on an update today and was wondering if it's related to TDE or not. Best, Michael The following packages will be upgraded: cups-browsed cups-filters cups-filters-core-drivers libcupsfilters1 libfontembed1 libkpathsea6 libptexenc1 libsynctex2 libtexlua52 libtexlua53 libtexluajit2 texlive-binaries ... Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ... install-info: warning: no info dir entry in `/usr/share/info/gtkdialog.info.gz'

2 2

konqueror man: ioslave weirdness
by J Leslie Turriff 21 May '23

21 May '23

I created a separate account with default settings, to do software development. In konqueror, I added a tab dedicated to man:/, but when I click on any of the man section links instead of opening them in that tab it sends them to Firefox(!) That doesn't happen in the konqueror in my regular account. What might be the cause? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 (x86_64) Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.0 tde-config: 1.0

3 4

14.1.0 is a sluggard so far :(
by Felix Miata 20 May '23

20 May '23

top - 15:39:53 up 18 min, 3 users, load average: 18.96, 18.45, 12.64 Tasks: 181 total, 19 running, 162 sleeping, 0 stopped, 0 zombie %Cpu(s): 82.3 us, 17.7 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15976.2 total, 14870.2 free, 352.4 used, 753.6 buff/cache MiB Swap: 1027.6 total, 1027.6 free, 0.0 used. 15339.7 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 828 root 20 0 53932 26496 21248 R 87.5 0.2 15:55.40 tdecryptocardwa 837 root 20 0 40064 9100 7040 R 87.5 0.1 16:11.58 dcopserver 1606 root 20 0 40200 9200 6912 R 50.0 0.1 3:11.87 dcopserver 1610 root 20 0 49856 21040 16816 R 43.8 0.1 3:13.08 kded 1634 root 20 0 52144 22548 17408 R 12.5 0.1 0:10.96 twin 1638 root 20 0 132284 25280 18972 S 12.5 0.2 0:20.96 kdesktop 1653 root 20 0 48084 16404 12544 R 12.5 0.1 0:09.00 kaccess 1664 root 20 0 58672 24980 18176 R 12.5 0.2 0:08.98 tderandrtray # rpmqa twin trinity-twin-14.1.0-1.fc37.x86_64 # inxi -CG CPU: Info: quad core model: AMD Phenom II X4 965 bits: 64 type: MCP cache: L2: 2 MiB Speed (MHz): avg: 3423 min/max: N/A cores: 1: 3423 2: 3423 3: 3423 4: 3423 Graphics: Device-1: NVIDIA GF108 [GeForce GT 630] driver: nouveau v: kernel Display: x11 server: X.Org v: 1.20.14 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau resolution: 1: 1680x1050~60Hz 2: 1920x1200~60Hz API: OpenGL v: 4.3 Mesa 23.0.3 renderer: NVC1 # From clicking login to finishing reloading of the prior session containing only Konsole and Help Center windows took ~50 seconds, with the vast majority of it on the fifth of seven icons blinking. Other upgrades from 14.0.13 to 14.1.0 seem to be similarly affected, Debian, Fedora, Mageia & openSUSE so far IIRC. Are others noticing this? -- 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

5 4

"The process for the sftp://192.168.1.7 protocol died unexpectedly."
by Curt Howland 18 May '23

18 May '23

Ok, this worked last week. Now it doesn't work. Debian Bullseye. Konqueror, "sftp://other-machine/" doesn't work anymore. I have one machine still using TDE 14.0.13, which I expected to work when the machines I updated to TDE 14.1.0 started acting this way, but no. Now none of them are able to sftp to each other in Konqueror. Ssh works just fine between the machines. I'm using shared keys, rather than passwords. Could that be the problem? The error is occurring instead of the pinentry dialog opening up. NB, the pinentry dialog opens just fine for kmail when signing this email. Suggestions? Curt- -- You may my glories and my state dispose, But not my griefs; still am I king of those. --- William Shakespeare, "Richard II"

5 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users