#Tag
Oh. Yay. Since upgrading to #Debian#Trixie a Suspend/Resume cycle kills kwin, firefox, bitwarden, signal, spotify and emacs on resume. Actually much more #KDE things than kwin, kwin is just the visible thing. Quick look in journalctl shows a whole load of those plasma-* dying. Right before there is Wayland dying. Probably should switch back to X11?
Need time for debugging, later somewhen. Not now.
First update for Debian 13: 13.1 released https://www.debian.org/News/2025/202500906 #debian #trixie #09
First update for Debian 13: 13.1 released https://www.debian.org/News/2025/202500906 #debian #trixie #09
Users of #GNOME#Evolution mail client: in #Debian13#Trixie, the Message-ID search (via command line) is broken. 😔
It got fixed already (see https://gitlab.gnome.org/GNOME/evolution/-/issues/3079) but the fix version 3.57.1+ is too new in comparison to the Debian version 3.56.1-1.
There is a workaround to do a manual search within the UI:
Search → Advanced Search: https://gnome.pages.gitlab.gnome.org/evolution/help/mail-searching.html
"Add Condition" → switch from "Sender" to "Free Form Expression"
mid:""
It will get fixed in Debian in four years. 🙄
HTH
Users of #GNOME#Evolution mail client: in #Debian13#Trixie, the Message-ID search (via command line) is broken. 😔
It got fixed already (see https://gitlab.gnome.org/GNOME/evolution/-/issues/3079) but the fix version 3.57.1+ is too new in comparison to the Debian version 3.56.1-1.
There is a workaround to do a manual search within the UI:
Search → Advanced Search: https://gnome.pages.gitlab.gnome.org/evolution/help/mail-searching.html
"Add Condition" → switch from "Sender" to "Free Form Expression"
mid:""
It will get fixed in Debian in four years. 🙄
HTH
Je vois un tutoriel sur installer Debian en LUKS, y compris la partition /boot
Pour cela il change la chiffrement de la partition LUKS de Argon2 en pdkf2
C'est un compromis de sécurité acceptable ?
Sinon, est-ce possible (et utile) de garder /boot hors du volume chiffré et de chiffrer /boot uniquement en pdkf2 ?
As some guys of you asked me to provide a #Debian #Trixie (13) final image as a #Proxmox compatible #LXC container template... There you go:
https://gyptazy.com/blog/debian-13-trixie-final-lxc-container-image-for-proxmox8-proxmox-9/
As some guys of you asked me to provide a #Debian #Trixie (13) final image as a #Proxmox compatible #LXC container template... There you go:
https://gyptazy.com/blog/debian-13-trixie-final-lxc-container-image-for-proxmox8-proxmox-9/
They *just* released version 142 and yeah, there's been a ton of focus on AI with these latest versions.
This tells me that my decision to delay upgrading to Trixie is probably wise.
Le dépôt « https://security.debian.org testing-security InRelease » a modifié sa valeur « Codename » de « trixie-security » à « forky-security »
Rejoice, I have updated the Proxmox homelab docs to Debian Trixie \o/
https://ergaster.org/posts/2025/08/04-overegineering-homelab/
I did an upgrade for my home server to #trixie
These third party things kept working.
Lyrion music server 9.0.1
Jellyfin 10.10.7
nextcloud 31.0.6
homeassistant core 2024.9.3 (with a backported python 3.12 in a virtual env)
For some reason the material skin add on in lyrion has disabled for me and I had to re-enable it
For some reason yggdrasil didn't automatically restart, I had to manually start it.
I had to move some php settings over into the 8.4 cli and fpm php.ini files for nextcloud
When upgrading postgres the old default timezone of US/Pacific didn't work and I changed the timezone to America/Los_Angeles in couple of variables in /etc/postgresql/${ver}/main/postgresql.conf
Installing tzdata-legacy would've probably also worked.
I need to update my home assistant environment to python 3.13 now.
I needed to install the new version of dovecot/conf.d/auth-system.conf.ext for dovecot to start correctly.
Anyone updated a very standard debian desktop install to Trixie, finding it unable to resolve (yes, it is DNS!).
DNS servers manually input in (stupid) default network manager graphical configuration tools (also manually set in stone in /etc/resolv.conf) can be pung... but no resolution happens...
#techsupport#itsDNS #debian #trixie #fcksystemd < in advance
A space for Bonfire maintainers and contributors to communicate
