tde-devels March 2026

devels@trinitydesktop.org

10 participants
4 discussions

Character encodings
by deloptes 18 Mar '26

18 Mar '26

Hi all, occasionally we have discussed issues with char encoding and the UTF-8 set. I can not recall what was done or discussed, so I want to ask first the community for common knowledge and then invest time in looking into code etc. I have following use case. I read a book with tde-ebook-reader. I can copy following text out of the book (example: “English: The 1931 Malay census was an alarm bell. IPA: ðə 1931 ˈmeɪleɪ ˈsɛnsəs wɑz ən əˈlɑrm bɛl.”) but in the reader the IPA characters are shown as squares. Is it a font issue, or encoding handling issue in tde-ebook-reader? -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

4 10

[François] [Gen2 iGPU] TDM locks up local I/O in Mageia 10
by Felix Miata 12 Mar '26

12 Mar '26

I realize using TDE for Mageia 9 on Mageia 10 can't be expected to be perfect, but there is no other option than to wait until built for it, and I've had good success for several releases until 10, starting last September. 10 is now in beta, so should only be some weeks until release. This particular case is on 32bit, so may have nothing to do with software versions other than end of support by Mesa for the Gen2 0x2572 iGPU. The thing is, same PC works just fine with Tumbleweed, KDM3, 6.18.9 and 6.19.6 kernels, and newer Mesa 26.0.1, while 10 has mesa 25.3.6. I'm hoping there is a way to rule out Mageia mesa and X problems prior to release of either 10 or 14.1.6. # systemctl status tdm ● tdm.service - Trinity Display Manager Loaded: loaded (/usr/lib/systemd/system/tdm.service; enabled; preset: disabled) Active: active (running) since Mon 2026-03-09 12:09:31 EDT; 28min ago Invocation: ff9b163fafed46f5918a23a3befbd915 Docs: man:tdm-trinity(1) Main PID: 958 (tdm) Tasks: 1 (limit: 3525) CPU: 753ms CGroup: /system.slice/tdm.service └─958 /opt/trinity/bin/tdm Mar 09 12:09:31 gx27c systemd[1]: Started Trinity Display Manager. # dmesg | grep -E 'aile|drm' [ 33.925764] systemd[1]: Starting Load Kernel Module drm... [ 34.604120] ACPI: bus type drm_connector registered [ 34.606161] systemd[1]: modprobe(a)drm.service: Deactivated successfully. [ 34.606688] systemd[1]: Finished Load Kernel Module drm. [ 38.043169] i915 0000:00:02.0: [drm] Found i865g (device ID 2572) integrated display version 2.00 stepping N/A [ 38.074479] i915 0000:00:02.0: [drm] Initialized overlay support. [ 38.075005] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 0 [ 38.123326] fbcon: i915drmfb (fb0) is primary device [ 38.207725] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device [ 40.298561] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2 [ 40.298583] cfg80211: failed to load regulatory.db # tail -18 /var/log/tdm.log X.Org X Server 1.21.1.21 X Protocol Version 11, Revision 0 Current Operating System: Linux gx27c 6.18.16-desktop-1.mga10 #1 SMP PREEMPT_DYNAMIC Wed Mar 4 21:26:12 UTC 2026 i686 Kernel command line: root=LABEL=mga10p19 rw audit=0 ipv6.disable=1 net.ifnames=0 plymouth.enable=0 noresume consoleblank=0 mitigations=off Build ID: x11-server 21.1.21-9.mga10 Current version of pixman: 0.46.4 Before reporting problems, check https://bugs.mageia.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 9 12:14:03 2026 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" MESA: warning: Driver does not support the 0x2572 PCI ID. Mar 9 12:15:03 tdm[958] error: X server startup timeout, terminating Mar 9 12:16:03 tdm[958] info: X server termination timeout, killing Mar 9 12:16:03 tdm[958] error: X server for display :0 can't be started, session disabled # journalctl -b -p3 Mar 09 12:09:25 gx27c rpcbind[593]: cannot create socket for udp6 Mar 09 12:09:25 gx27c rpcbind[593]: cannot create socket for tcp6 Mar 09 12:09:31 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:31 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:31 gx27c rpc.statd[955]: Failed to create listener xprt (statd, 1, udp6) Mar 09 12:09:32 gx27c rpc.statd[955]: Failed to create listener xprt (statd, 1, tcp6) Mar 09 12:09:32 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:32 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:32 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol Mar 09 12:09:32 gx27c rpc.mountd[942]: Could not make a socket: (97) Address family not supported by protocol No such problem in Tumbleweed and KDM3 with 6.18.9 or 6.19.6 kernels: # pinxi -GSaz --vs --za --hostname pinxi 3.3.40-01 (2025-11-25) System: Host: gx27c Kernel: 6.19.6-1-default arch: i686 bits: 32 compiler: gcc v: 15.2.1 clocksource: tsc avail: hpet,acpi_pm parameters: root=/dev/sda10 rw ipv6.disable=1 net.ifnames=0 noresume consoleblank=0 mitigations=off Desktop: KDE v: 3.5.10 tk: Qt v: 3.3.8c wm: kwin with: kicker vt: 7 dm: 1: KDM note: stopped 2: XDM Distro: openSUSE Tumbleweed 20260308 Graphics: Device-1: Intel 82865G Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen-2 process: Intel 130nm built: 2002-03 ports: active: VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2572 class-ID: 0300 Display: x11 server: X.Org v: 21.1.21 compositor: kwin driver: X: loaded: intel unloaded: modesetting alternate: fbdev,vesa dri: swrast gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1680x1050 s-dpi: 108 s-size: 395x246mm (15.55x9.69") s-diag: 465mm (18.32") Monitor-1: VGA-1 mapped: VGA1 model: Dell P2213 serial: <filter> built: 2013 res: mode: 1680x1050 hz: 60 scale: 100% (1) dpi: 91 gamma: 1.2 size: 470x300mm (18.5x11.81") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: EGL Message: Unreliable API tool+hardware. Override with --egl. API: OpenGL v: 4.5 vendor: mesa v: 26.0.1 glx-v: 1.4 es-v: 3.2 direct-render: yes renderer: llvmpipe (LLVM 21.1.8 128 bits) device-ID: ffffffff:ffffffff memory: 1.42 GiB unified: yes API: Vulkan v: 1.4.341 layers: 2 device: 0 type: cpu name: llvmpipe (LLVM 21.1.8 128 bits) driver: mesa llvmpipe v: 26.0.1 (LLVM 21.1.8) device-ID: 10005:0000 surfaces: N/A Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo x11: xdriinfo, xdpyinfo, xprop, xrandr # free total used free shared buff/cache available Mem: 1522856 425816 858464 80332 496048 1097040 Swap: 1052220 0 1052220 # -- 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

3 3

Why are all the source archives bad?
by E. Liddell 08 Mar '26

08 Mar '26

When upgrading to 14.1.4 and then to 14.1.5, I was bombarded with the following messages indicating the .tar.xz files have some issue: * Messages for package trinity-base/kcheckpass-14.1.5: * tar extract command failed at least partially - continuing anyway * Messages for package trinity-base/tdm-14.1.5: * tar extract command failed at least partially - continuing anyway * Messages for package trinity-base/kdesktop-14.1.5: * tar extract command failed at least partially - continuing anyway This happens for all the TDE core packages (but not for k3b). I don't remember whether it was an issue with versions before 14.1.4. It would just be a mildly irritating bit of log spam except for one thing: one of my machines is behind a corporate firewall that I do not control, and it *hates* compressed files it can't open and inspect. So I have to move the files to it via sneakernet. Is whatever method is being used to create these files adding trailing garbage or something? E. Liddell

3 4

Getting SMTP connection error when attempting to upload mail to mail.com
by jlt1 04 Mar '26

04 Mar '26

For some reason, for several days now when KMail tries to upload mail to smtp.mail.com I get the following message: | Sending failed: | | Connection to host smtp.mail.com is broken. | | The message will stay in the 'outbox' folder until you either fix the problem (e.g. a broken address) or remove the message from the 'outbox' folder. | | The following transport protocol was used: | | mail.com I have tried deleting and recreating my settings for outbound mail in KMail's Settings => Accounts, Sending but that hasn't fixed the problem. I am able to ping smtp.mail.com, so the server is reachable. Is anyone else having issues connecting to SMTP servers? Leslie (sent via the mail.com web interface)

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels March 2026