tde-devels August 2026

devels@trinitydesktop.org

9 participants
6 discussions

TDM greeter on 2 of 3 displays???
by Felix Miata 30 Aug '26

30 Aug '26

I used TDM always in un-themed configuration, so tdmrc is never OEM here. When I boot with two displays connected, greeter shows up on only one. When I boot with three displays connected, greeter shows up on two of three. Are two of three expected? Controllable? -- 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

Questions and observations from the Brazilian Portuguese translation review
by Sebastião Guerra 14 Aug '26

14 Aug '26

Hi all, I have been working on a fairly broad review of the Brazilian Portuguese (pt_BR) translation of TDE, and after spending some time with the existing catalogs I thought it would be useful to share a few observations and, more importantly, ask about the preferred workflow before I go much further. My initial goal was simply to review and complete the pt_BR translation, but the work has gradually become more systematic. I have been reviewing the PO files, checking Weblate warnings and consistency issues, comparing questionable strings with their source/templates, and also building the current TDE Git sources so that I can check translations in their actual UI context rather than only looking at the catalogs. One thing that became apparent is how much history there is in these translations. Some strings have apparently survived from KDE 3.x-era translations, sometimes with terminology or wording that no longer seems appropriate, while other inconsistencies seem to come from later revisions. In a few cases, what initially looked like a translation problem turned out not to be one. I have also encountered cases where the problem seems to be in the source translation template rather than in pt_BR itself. This includes inconsistencies in POT/PO structure, plural-related issues, unusual source strings or context, and cases where Weblate's validation exposes something that is difficult or impossible to fix correctly only from the translation side. This raises a question about how you would prefer these cases to be reported. If a problem is clearly in a POT/template or ultimately in the application source, should I open an issue against the corresponding TDE component, report it here first, or use some other workflow? I would like to avoid creating unnecessary issues while still separating actual translation problems from problems that need to be fixed upstream. I also have a question about reviewed translations. As I go through pt_BR, there are strings that I can not only translate but also verify in context in a current TDE build. Once such a translation has been reviewed and tested, is there any TDE policy or Weblate mechanism for considering it "reviewed" or "approved"? I do not mean making a translation immutable — there will obviously always be legitimate reasons to improve or correct it. My concern is avoiding unnecessary changes to translations that have already been carefully reviewed and tested in context. Does TDE make use of Weblate's review/approval features or permissions for this purpose? If not, is there an established convention among translation teams for this? There is one more part of the translation tree about which I am unsure: the documentation. I noticed that the DocBook documentation/manual translations do not seem to appear in Weblate, at least not in the same way as the application PO catalogs. I may simply have overlooked the appropriate project or workflow. What is the recommended way to work on those translations? Are the DocBook/manual translations managed through Weblate somewhere, or should changes to them be prepared directly against the TDE internationalization/translation Git repository and submitted as normal Git changes/pull requests? I am asking these questions now because I would like the pt_BR review to follow the project's preferred workflow rather than establish my own assumptions about how translations should be maintained. My intention is ultimately to leave the Brazilian Portuguese translation in a state where it is not only more complete, but also internally consistent and checked against the applications wherever practical. While doing this, I am keeping track of cases that appear to be translation issues separately from those that may originate in templates or source code. Any guidance on the preferred workflow for these cases would be very welcome. Thanks, Sebastião Guerra

2 1

Re: Weblate Translation Workspace - 502 Bad Gateway Error
by Slávek Banko 13 Aug '26

13 Aug '26

On Monday 03 of August 2026 14:42:43 Mustafa Sezer Yılmaz wrote: > Hi TDE Team, > > I am trying to access the TDE Weblate Translation Workspace at > https://mirror.git.trinitydesktop.org/weblate/ to contribute to the > Turkish (tr) localization. > > However, the server currently returns a "502 Bad Gateway" error and is > inaccessible. > > Could you please check the status of the Weblate server? Do you have an > estimate on when it might be back online? > > Thank you for your great work on the Trinity Desktop Project. > > Best regards, > > 3 Ağu 2026 Pzt 3:30 PM tarihinde <weblate(a)trinitydesktop.net> şunu yazdı: > > Your registration on TDE Weblate > > > > This is an automatic e-mail to help you complete your registration > > with TDE Weblate. Please click on the confirmation button below. In > > case it doesn't work you might need to copy the URL on next line into > > the browser address bar to proceed. > > > > https://mirror.git.trinitydesktop.org/weblate/accounts/complete/email/ > >?verification_code=5b69ea3143904e1998057a0ed39c0526&partial_token=fc637 > >3cffa8a438bb10bd80f1f8ccd95 > > > > The confirmation link will expire after 48 hours. > > Confirm registration > > <https://mirror.git.trinitydesktop.org/weblate/accounts/complete/email > >/?verification_code=5b69ea3143904e1998057a0ed39c0526&partial_token=fc63 > >73cffa8a438bb10bd80f1f8ccd95> > > > > If there is a problem with your registration, please contact us. > > <https://mirror.git.trinitydesktop.org/weblate/contact/?t=reg> > > > > > > Weblate, the libre continuous localization system. > > <https://weblate.org/> > > > > Generated on Aug. 3, 2026, 12:30 p.m.. Hi Mustafa, all, similar to what happened with TGW some time ago, TWTW started to get overloaded with "awesome" AI agents. Because of this, the server could sometimes give 502. Yesterday I successfully activated the same solution as used on TGW - we added access throttling using Anubis. I hope this helps get the server load back to an acceptable level, and that TWTW will work well for users again. Cheers Slávek --

1 0

Frequency of PSB package updates
by Sebastião Guerra 12 Aug '26

12 Aug '26

Hello, I am currently translating and reviewing the Brazilian Portuguese translations of TDE. In addition to completing untranslated strings, I am also working on terminology consistency across the different applications and components. I would like to know how often the preliminary build packages are rebuilt and published. After a translation is submitted and accepted through Weblate, approximately how long does it usually take for that change to become available in the preliminary build repositories? Knowing the usual update frequency would help me test the translations in a running TDE environment and identify inconsistencies more efficiently. Thank you for your help. Best regards, Sebastião Guerra

3 3

tmix - replacement for kmix for pulseaudio.
by Calvin Morrison 11 Aug '26

11 Aug '26

hi guys, please see this repo and give feedback if you cane it is a pulseaudio based mixer for TDE. it's similar to kmix but not identical. It's similar to pavucontrol-qt but not identical. If you can build it, let me know, if you cannot build it, let me know if you like it... let me know! maybe it could go upstream at some point into tdemultimedia, it would take work, translations, a help guide, probably minimally also an ALSA backend as well. https://git.ceux.org/tmix.git/ thank you all

7 44

[François] Mageia upgrade from 9 to 10 refuses to upgrade any TDE packages due to signature key not trusted
by Felix Miata 01 Aug '26

01 Aug '26

Mageia 10 was released yesterday, but upgrading from freshly upgraded 9 32bit, it refuses to upgrade any trinity rpm due to NOT TRUSTED signature key As urpmi --auto-update downloaded all v10 packages, I was able to force install them with rpm, which was very tedious, but TDE & TDM are working. -- 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 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels August 2026