Firefox on Debian stable is so old that websites yell at you to upgrade to a newer browser. And last time I tried installing Debian testing (or was it debian unstable?), the installer shat itself trying to make the bootloader. After I got it to boot, apt refused to work because of a missing symlink to busybox. Why on earth do they even need busybox if the base install already comes with full gnu coreutils? I remember Debian as the distro that Just Wroks™, when did it all go so wrong? Is anyone else here having similar issues, or am I doing something wrong?
I use debian headless as a server never had any issues but then again pretty much any linux system is gonna be a decent server since everything is containerised now.
You are literally describing the idea of Debian. Yes, stable is old, but that is the whole purpose. You get (mostly) security updates only for a few years. No big updates, no surprises. Great for stuff like company PCs, servers, and other systems you want to just work™ with minimal admin work.
And testing is, well, for testing. Ironing out bugs and preparing the next stable. Although what you describes sounds more like unstable, the one where they explicitly say that they will break stuff to try out other stuff.
So, everything works as intended and advertised here. If you want a different approach to stability, I guess you will have to use a different distro, sorry.
I guess when you last tried it, it was at a time when a new stable came out, so testing was more or less equal to stable.
About the firefox: It ships Firefox ESR these days, meaning you get an older, less often updated tested firefox (with security updates, of course). Again, this is the whole point. Less updates, less admin work, more time to find and fix bugs. Remember the whole Quantum add-on mess, for example?
As others have said, you can install other versions of firefox (like the “normal” one) via flatpak, snap… nowadays.
This is why Debian is my server of choice, and my work desktop of choice.
OP, There are some flavors of Debian out there that are more rapid release, like LMDE, Siduction, Sparky, even Kali (though I wouldn’t recommend Kali as a primary desktop personally). Some based on Sid, some based on Testing.
The last paragraph is vital. Grab a flatpak of any software you need to be more up to date. Flatpaks running on Debian are amazing. Current software running on a stable base.
You can install Firefox from Mozilla’s own repository. It is a luxury to have in Debian a Mozilla repository to install Firefox.
Arch is where the cool kids put in the work these days. There philosophy of downstream packages untouched results in fewer problems and easier maintenance. Why would anyone be a package maintainer for Debian? It’s a thankless task, and hard
the work amount of backporting fixes which ARE already fixed in newer versions is also insane
thats one of the reason why Arch Linux sticks to stable upstream versions, backporting is just not feasable on smaller teams
I have been an Arch user for years now and anytime I touch a debian based distro it is such a headache: weird patched packages that don’t compile anything past or present, insta dependency hell with PPAs, package names of 200 characters because apt doesn’t have a good way to represent metadata… It made me a strong believer that trying to fight the bit rot and stick to the old stuff is counterproductive: a consistent head based development with a good community fixing bugs super quickly results in less hours of work fighting the paleolithic era dependencies, safer (as security fixes are faster to get in, packages are foreign to hackers and constantly changing etc), easier to find documentation as you don’t need to dig into history to find which option existed or not, recent stuff is also easier to support for the developers of the various packages as it is fresh in their minds. Another point is to look at it from a tech debt lens: either you fix your stuff to work with current deps now or you just accumulate tech debt for the next engineer to fix in a way larger and combining a mountain of breakages in the future that of course IT and SREs will never want to do until the 15y old software is a disaster of security issues…
Stable is for servers, unstable for desktop. It has worked for 20 years. I actually installed two further Debian workstations recently after trying and failing with Kubuntu. So … no, I don’t have this problem.
No idea why busybox is needed. Is this is your emergency boot environment like initramfs? Sometimes it’s nice that Linux boots up and offers an environment to fix stuff while some modules are broken.
Busybox is used in the initramfs normally. It’s the shell used by any scripts in that early stage, as well as the fallback shell environment.
Or there is OpenSuse Tumbleweed which is up to date, and stable…
Tried the Tumbleweed. It’s anything but stable.
As someone who has used it for a few years. Incorrect. I had one upgrade issue (from KDE 5 to 6). Other than that. Smooth. For the Plasma upgrade, just change to default them before upgrade and upgrade from command line, not terminal window.
Stable, in this context, just means “point release”. If you meant “doesn’t break”, that describes most rolling release distros.
…unless you’ve used KDE in the last month. Holy cow, just let me alt-tab into a fullscreen window without throwing a fit.
Never had issues due to ‘outdated’ packages myself, but then again, I wasn’t into the latest & greatest.
I mean, you’re always free to choose something else instead of bitching.
Huh? Install testing or sid?
The Debian way is to install stable then change your sources.list to either testing or unstable.
I call shenanigans.
edit: what version was Stable using before 11Jun? 'cause it’s 115.12.0esr-1 right now.
Thats not a good idea unless you do a proper upgrade (dist upgrade or similar)
It is easier to use the testing iso
the wiki must be out of date then
You can try this:
Even has BTRFS setup with Snapper (or Timeshift maybe) and nala is an option.
https://www.theregister.com/2023/01/05/siduction_2022_1/ Overview.
I’ve been on Debian Testing for my own desktops for about 15 years now. Sometimes as a Frankendebian mixing in SID/unstable. Sometimes mainly unstable, but mostly just Testing.
It rarely breaks, but when it does, it’s a learning opportunity. Stable for servers and other people’s desktops. Maybe with backports. Flatpacks if this no other option.
You don’t get 100% solid and 100% new. Ever. With anything.
A someone who worked in OS security, I beg you dont use flatpaks.
As someone who works, flatpak’s solve a bunch of problems, freeing me up to continue working.
Security issues are just a class of issue; no more or less important than other issues
As I said, “if this no other option”. And to be honest, that was once, for a few weeks before the new KiCad hit Debian repos. And only because hardware team wouldn’t wait to switch, so to open stuff, I needed it too.
Debian is working as intended. You are wanting to use Ubuntu or Mint if you want more up to date packages.
If the user really wants a new browser, Flatpak is always an option.
They also have a .deb you can manually update as well.
They can just use Flatpak as it will be the newest outside of Arch. Alternatively they could run Distrobox with something like Fedora.
I stopped using flatpak when I found out both I had to update outside of the package manager. Also using flatpak gave me some issues with my sound card, so I just run the .deb. To each their own though, which is why I love Linux.
really?, thats your argument “need to use an outside package manager”, anti-flatpak argument are each day becoming more unhinged lmao
Again, not arguing against, just why I don’t…. You do you, I’m just talking about me. Just cause I don’t use something for some reason doesn’t make me anti that thing. Linux community can be so volatile sometimes
fair, that i heard so much shit about people hating flatpak when it can be very helpful for newcomers that it got to my head, sorry
It can be tough through words to understand intent sometimes, and I to write sarcastic and dry, so no problem.
Flatpak is helpful, it’s how I ran several programs before my work forced me to windows, it does have its place in the toolbox.
https://wiki.debian.org/DontBreakDebian
Installing outside packages is generally not a good idea. You can use Distrobox with a upstream distro like Fedora or you can use Debian Back ports.
Had forgotten about backports. Need to get that set back up. Thank you for the reminder.
Ever considered LMDE? Best of both worlds if you ask me.
Someone after my own heart… Debian for my servers, lmde for my laptop, the way it was meant to be.
I’m considering moving to Debian Stable plus Flathub for graphical desktop packages like Firefox, it works well on the Steam Deck. SteamOS also provides Distrobox which helps in some cases.
Flatpak is awesome, I love it so much. It lets users pick a distro based on the unique features that distro provides, without having to worry about whether their favourite apps are packaged. Since you’re considering switching to debian+flatpak, here is a list of pitfalls I’ve run into in flatpak so far, maybe this can save you some troubleshooting:
- You need to have a thing called an “xdg dekstop portal” installed. Otherwise filepickers will be broken. On Debian this should be a dependency of flatpak, so it should be installed by default tho.
- If you’re manually restarting Xorg without using a display manager, make sure the xdg desktop portal process doesn’t get started twice. Otherwise it will be broken
- As far as I understand, there’s no way to use xdg desktop portal to forward an entire directory through to a flatpak’d app, unless the app itself asks specifically for a directory. So stuff like opening a
.htmlfile that references a.cssfile in the same directory with a flatpak’d browser will be broken, unless you manually make an exception using Flatseal orflatpak override. - Make sure your root filesystem is mounted with “shared” propagation, otherwise
umountcommands won’t propagate into flatpak’s sandbox, and drives will get stuck in a weird state where they’re mounted in some namespaces, but not others. This should be the default in Debian tho. - If flatpak’d Firefox has ugly bitmap fonts, follow this workaround
Anyway, this is just my experience running Flatapk in Void, hopefully it works smoother for you on Debian.
Debian Stable ± Flatpak gets best of both worlds
For me, the outdated packages in stable have actually gotten better over time, as DEs get closer to a place where I don’t need any major updates to enjoy using them, Flatpaks become more readily available, and on a subjective level, I get less and less invested in current Linux news. Before Debian became my “forever distro”, I’d hopped to it a few times, and often found myself wishing for a newer piece of software that wasn’t in backports or flathub, or simply being bored with how stable it is, but that’s been happening less and less. And I feel like Debian 12 in particular left me with software that I wouldn’t mind being stuck with for two years.
I’ve gotten warnings to upgrade my browser with Debian’s Firefox ESR, but they never affected a website’s usability in a way that a newer version would fix, and they do provide security updates and new ESR series when they come out; even if you must have the newest Firefox, you can use the Flatpak.
Additionally, I’m currently on testing in order to get better support for my GPU, and each time I’ve tried to use it, it’s worked for me for a longer time than the last as I get better at resolving or avoiding broken packages. If you do experience issues like the one you described, and can replicate them, and no one else has already reported them, you should report them to Debian’s bug tracker. The whole point of Testing is to find and squash all the critical bugs before the next stable releases.
You must not be using an Nvidia GPU on Wayland because KDE is pushing updates for this use case
OP when they try Debian and it’s exactly what it advertises itself as:
