Mason PinesJun 6, 2025

Spent the evening upgrading from #debian #bookworm as the current stable to #trixie (which is still testing but is now well into freeze, so little will change for everyday use).

Checked the draft release notes and did the inline upgrade. Mostly okay.

Annoyances were from having to set up virtual environments again for #python apps. I tend to use #pipx and couldn't just do an upgrade, I had to refresh the #python runtime within each #pipx venv. Bit annoying, but not too onerous.

Main issue stems from a couple of apps that are not in the #debian repos.
#dvbcut hasn't been updated to be #trixie compliant, and that isn't available as #appimage or #flatpak, so that will be something I'll lose until I can sort out a docker or VM to run it if I truly need it still.
Other was trying to get #avidemux to compile and run - several fruitless hours later, and that isn't working either. For now I've gone with the flatpak but it's not official and I don't really like flatpaks if I can avoid them.

Show threadBryanJun 6, 2025
@mp362 I tried Trixie but it just isn't ready for everyday use for me. It is almost there I think and it is great for people who understand it will take a lot of work to make it work full time. I had to switch back to Stable.
Show threadMason Pines

@resplendent606
Yeah, I'm coming to the same conclusion.
The core is fine, but all the little papercut issues add to stability problems, even on good old #xfce, which is the DE I run.

I will do another backup, then reformat and reinstall #bookworm stable.

I'll continue to monitor the progress of #trixie within a VM under virt-manager, and try to resolve the handful of key issues holding me back.

At some point, I will have to upgrade to it, but that isn't for at least a year after #trixie is released, as #bookworm will continue to receive security updates until then.

Jun 7, 2025 at 8:33amWeb
Show threadMason PinesJun 9, 2025

@resplendent606

I finished my switch back to #debian #bookworm

I did still have some new issues that I didn't from when I'd originally installed #bookworm at release 12.1, and it seems since then some updates create a few niggles with certain self-compiles.

Resolved the last of my libqt5widget trackback errors by setting #qt5ct back to gtk2 rather than #kvantum. For whatever reason, that combination caused applications like #avidemux to fail to run. I had issues compiling that as well, but overcame them by fixing a typo in one of the cmake files.

Anyway, back to a stable and working environment.

Going to spend time in a virt-manager VM to test out #trixie as a clean install with #kde as the DE. I think having KDE as the base DE and then setting #gtk theme support is the better way around, and more of the apps I now run are Qt-based nowadays, and that seems to be a trend that is growing.