I usually only run LTS versions, but I've hit quite a few speed-bumps on 18.04 and have been quite surprised that many prominent software packages are deploying fixes to 19.04 only, and not adding fixes to 18.04.
Full disclosure: All my data is on a NAS and so I'm resistant to sandboxes. So this is mostly apt related.
I imagine it's a kernel issue, but it still poses quite a problem. I find myself using debs and adding 3rd party repos more with 18.04 than with any other release.
Bluetooth, gnome apps like gimp, flatpak - all have a number of workarounds to get working in 18.04.
E.g.
GIMP version in the 18.04 repo is 2.8., with several things broken. When I finally had no workaround for cage transform tool error, I dug deep and found that I couldn't rely on the canonical repo.
Fixes are in latest version and Gimp approach to get 2.10 is either use flatpak or compile (though it is in snap - if you only save files locally).
flatpak is a somewhat ironic example, being an alternative to apt I'd imagine they want to give apt users the best opportunity to experience flatpak, but there's only a very old v1.0.8 in the 18.04 repo, and only when you visit https://flatpak.org/setup/Ubuntu/ do you find that adding a 3rd party repo gives the latest 1.4.2. But you'd never actually ever get to know about this unless you went deeper into flatpak docs, which probably only happens when something has already gone wrong
Flatpak are maintaining in 18.10 onwards only: https://flatpak.org/setup/Ubuntu/
E.g. Bluetooth / Bluez is broken in 18.04, with no apparent appetite to backport the fix. Add repo to workaround
https://askubuntu.com/questions/1036...untu-18-04-lts
I haven't kept a list, but I'd say I've stumbled across at least 8-10 apt packages recently which are not being fixed in 18.04, only later versions.
Which sort of breaks the LTS concept for me. Thoughts?
Bookmarks