For those – like me – that more or less forgot that Debian 13 is the new “stable” distribution (since August 9th, 2025), I advise them to check their APT configuration!
My configuration was still set so that only the “testing” repository was used, and after friday updates, the Xorg was broken… I guess because the qubes repository was (correctly) set to use 13. So I started back with the last backup and changed the repositories & pinning, and now everything is OK again.
I know I could (should?) use the toy names of the distros (e.g. trixie & forky) but I can never remember who is what so I always use “stable”, “testing” & “unstable” which make the logs much clearer for me.
I know I could (should?) use the toy names of the distros (e.g. trixie
& forky) but I can never remember who is what so I always use
“stable”, “testing” & “unstable” which make the logs much clearer for
me.
I always use the toy story character names for my debian.sources
files.
You raise a good point… why did I move away from the official template? I don’t really remember!
When looking at the different profiles given in How to organize your qubes — Qubes OS Documentation, I am the Alice kind (i.e. software developer). So I guess I needed versions from unstable for some tools.
It was also my first experiments with Qubes and I tested a lot of things… I tried to highly fine-tune the template so creating a new VM for a new project was very quick. But I spent way too much time on that for a result that wasn’t that good.
And now that I move away from nearly only C++ to several other languages, the settings are becoming a nightmare. So I slowly switch to an untouched template with mise-en-place for handling the versions of the projects.
I guess because the qubes repository was (correctly) set to use 13. So I started back with the last backup and changed the repositories & pinning, and now everything is OK again.
