Normally I always forget why I still keep thinking about switching back to Windows. Today was a great reminder. Linux can be frustrating. This post is somewhat about awareness and partly about me learning about other peoples experiences. I updated my CachyOS as usual. There were some system packages upgraded and I got the notification to reboot. Figuring I’d do it later I left after some time and the PC went to sleep. Upon returning the screen stayed black. Even upon forced reboot. Remembering I was using Limine with BTRFS snapshots I tried multiple previous snapshots but to no avail. I remember this happened before. So now I face another reinstall… This and having to dive into the deep end of terminal commands to get drivers, programs or games working can be quite frustrating. I understand why people are turned off and go back to Windows…
Onto NixOS for me. A big dive but it seems very stable which might be just what i need. I feel like the philosophy of NixOS combined with a graphical store to install programs and what not seems like a great solution.
What would your ultimate distro be like?
Fedora w/ KDE always just feels like home to me, I like the defaults so I don’t spend much time mucking around, and it feels stable and reliable.
This is exactly what I think every time someone recommends CachyOS or Manjaro to new users. Arch is great, but it expects the user to know how to deal with things, it expects user to read the news and it pulls the rug periodically because it expects you to be able to figure things out.
In your case in particular I don’t think it was Cachy on its own, otherwise we would have seen other users affected, but still, it’s likely that the Arch philosophy got you because of something you changed without even remembering and now with the update your config is no longer backwards compatible.
NixOS is great, but it’s a very different paradigm, you will not be able to install things from the graphical interface as you’re expected to declare your system. And it can never be compatible with a graphical installation as that would beat the whole purpose of reproductible builds.
I think what you’re looking for might be something like Bazzite, where the core system is immutable but you get user space freedom. But personally, if 0 downtime is your goal NixOS is better, as you can rollback to previous generations of your system if something goes wrong, but to get that you have to pay the price of declaring your whole system which might be too steep to pay for some.
cachyos is not a system for newbies, or absolute stability. nix isn’t it either.
try fedora, debian,
ubuntu, mint or something newbie friendly if you want a newbie friendly experience.I use fedora, debian and mint because I have several computers for different usecases. I wouldn’t recommend Fedora for this, all the others are gold in my experience, but newbies really should go through Mint first.
i find that bazzite can be a great beginner distro, as it has some sane quality of life defaults baked in over fedora, but fedora is not bad if you can get used to default dockless gnome for example.
I’d argue that CachyOS is more noon friendly than arch. As would EndeavourOS be. People fail to see my point that sometimes Linux breaks very easily and I’m not blaming Cachy or Arch specifically but a simple update and sleep should not result in a black screen on any OS IMO. It’s just off putting… If this would happen on windows I’d definitely complain too. And there have been plenty of instances where microslop added OS breaking things…
you are arguing from a place of stubbornness. cachy arch and nix are not supposed to be newbie friendly distros. linux doesn’t break easily at all, but only if you accept you need the right tool for that job.
it’s like that youtuber that keeps insisting on using pop os with a beta desktop when he knows its not windows and breaks, and then complains it’s not windows and breaks.
i work with linux and i’ve been updating hundreds of debian, ubuntu and assorted turnkey distros over decades without issue, and you could too.
I was never talking about either of them being noon friendly. Also, updating and failing to boot is kind of breaking easily I’d say. So I don’t get what point you’re even making.
so one of the reasons distros that update quicker and use newer software are generally considered advanced is because they use brand new less tested software that breaks easier. ie. for enthusiasts looking for all the new shiny features all the time, the best possible performance or easy modularity at the cost of stability.
it’s what i mean when i say you have to accept you need the right tool for the job. newbies who expect and need a stable hands-off experience like you are recommended debian, mint, ubuntu and such for a reason.
don’t worry though, the cool new features and performance will trickle down to you whenever they are ready for wide adoption. and you can be an enthusiast on a boring distro too.
simple update and sleep should not result in a black screen on any OS IMO
That’s the thing. Different distros handle it in different ways. Some have the option to do offline updates so it will not actually install the update until after reboot so there is minimal risk of something interfering. That’s why often the recommendation is to try and find one that is more stable if that is what you value more.
I can totally get behind that. But then I’m left wondering: if that approach minimises the risk of interference, then why don’t all distros work that way?
My guess would be some value stability at all costs, others value user control, and others value uptime.
I’d argue that CachyOS is more noon friendly than arch.
I’d say no, Arch forces you to learn to use a terminal, chroot and other things so you can fix your system if it breaks. CachyOS expects you to know this but doesn’t force you to. It’s like saying jumping off an airplane is more noob friendly because of the static line.
People fail to see my point that sometimes Linux breaks very easily and I’m not blaming Cachy or Arch specifically but a simple update and sleep should not result in a black screen on any OS IMO.
Yes, that’s correct, I have never ever in my 20 years of running Linux and administering Linux laboratories seen a system break because of a sleep during an update. It’s very likely that that was just a coincidence and the system would have broken regardless of the sleep. I don’t have all of the info but my guess would be either Nvidia driver related (as I see recent news mention it on both Arch and Cachy) or (more likely) you changed a system config and the update kept your version which is now not compatible (it happens, it’s part of the reason why Arch is called unstable, on stable distros that can only happen during version updates, and you get promoted about each of them, but Arch expects you to check pacnew/pacsave files after an update)
It’s you who’s missing the point that the other person made, your experience is not something that matches other Linux users. CachyOS is not noob friendly, these sort of thing should never happen in Mint or other more noob friendly, but Cachy expects you to be aware of certain things because it is a bleeding edge rolling release distro. People think Arch is difficult because of the installation process, but that’s not it, that’s very straightforward, maintain the system is what’s difficult.
As a newbie it is easier to set up Cachy. When shit hits the fan either fixing it on Arch or Cachy would give a similar experience to a noob I think.
I understand it might be a fluke or that I am at least a minority in this issue. But that makes troubleshooting harder. I’m even on all AMD hardware.
It’s interesting that the whole idea about stability (the system not breaking) shifts from the developer to the user.
As a newbie it is easier to set up Cachy. When shit hits the fan either fixing it on Arch or Cachy would give a similar experience to a noob I think.
Yes, but Arch prepared you for it. Arch philosophy is one of teaching you why you need to do something, and then how to do it, so if something breaks you have some vague idea of what was and how to fix it. CachyOS is Arch, it has the same expectations of you knowing things, and having read the wiki, but you skipped the tutorial. This is why me and many others despite the idea of recommending an “easy” Arch to newbies, it’s not easy and only causes trouble.
Arch is very unstable (in the sense that anything can change) and that means it’s easier to break things if you’re not careful with things you don’t know to be careful about. For example, not saying that this is your case, but I’ve seen people install drivers and programs through binaries downloaded form a webpage like they would on Windows, that is a TERRIBLE idea as it will likely break on the next update, and if it’s something important like a GPU driver you will be dropped to a terminal.
I understand it might be a fluke or that I am at least a minority in this issue. But that makes troubleshooting harder.
It’s not about being a minority, it’s about we don’t have all of the info so can’t help you. From the info you gave us I can tell you it’s not something known, as I haven’t seen it being reported by others, which means it’s something specific that you did to your system. Every thread I find for CachyOS update breaking things is a unique case where the person did something.
And I know your knee jerk reaction will be “I did nothing, I only updated”, but that’s probably not true, otherwise we would see other people reporting the issue. If simply updating now was enough to break the system we would be hearing from hundreds of people whose system broke. But we haven’t, the only report we have is yours, which very likely means you did something different from everyone else. And I get that you don’t know what it is, when I first started using Linux I used to break my system every couple of months, and I always thought it was the system fault, but guess what? It wasn’t. Eventually I learnt to use Linux and my system never broke again, I can’t tell you for sure what I was doing before, but clearly I was doing something.
It’s interesting that the whole idea about stability (the system not breaking) shifts from the developer to the user.
Well, that’s bound to happen if you own the system. Same reason most companies have a warranty void if you fiddle with the internals, once you do that it’s impossible to say if the issue was caused by you or them, and the same thing is true for a Linux system. My guess here is that you changed a config, or installed an unofficial package or something or the sort, it might have been months ago, but now the update changed one of the underlying things and it broke. I would probably lean to the config side of things, since I don’t expect you installed anything critical from outside the repos. Or another possibility is that you went a long time without updating, that can have consequences on Arch systems.
PS: I get it, I know this seems harsh, I know you’re probably thinking “I did nothing, this Linux is unstable and finicky”, I know that because I was in your shoes 20 years ago. Arch is not for everyone, even some extremely knowledgeable people dislike the high maintenance it sometimes imposes, for new people without experience it can be like walking on a landmine field. Which is why I always recommended more newbie friendly distros like Mint, because they try to be more stable in all senses of the word (you can still break them though, as you are in control of the system, but it’s more difficult).
Use something stable and boring like LinuxMint. No issues in 7 years.
Why reinstall instead of just repairing the issue at hand?
We had to do that in Windows too.
Hard to repair with no image. And fixing it using a live USB with root is quite involving. Windows issues are almost never this serious and in such cases safe mode exists.
I have found bazzite to be very stable for my needs. My use case is mainly gaming with some light productivity. I have had very few problems.
I switched a couple of days ago. Seems very good so far!
Ubuntu was the first Linux distro I tried, and I’ve never tried anything else, across three laptops. I’ve never experienced problems like the ones you describe.
I know its frustrating when this happens. But there is something called arch-chroot, its a program to fix your messesd up os. New users don’t know about this, but as you keep using Linux, you get familiar to these programs. It takes few mins to fix broken system using arch-chroot. I hopw your system won’t break anymore.
I see people recommending Debian but you also said you enjoy tinkering, so I’d recommend SpiralLinux. It’s basically Debian but it uses BTRFS so you can roll back to a previous snapshot if you break something. I don’t think Spiral has updated to Trixie yet so you’d need to manually upgrade but that’s not too big a hassle if you do it immediately.
I think NixOS is a superb choice if you have the time and energy to invest in it. I’m currently using Guix System (a GNU fork of Nix) and I’m very very happy with it. Previously I’ve been on openSUSE Tumbleweed because I thought the most important thing for me was btrfs with an easy snapshot system. But then, one day, when I was writing ansible playbooks to configure my OS I realized that what I care most about is declarative configurations. Now I’ve completely stopped using ansible for my laptop/desktop, and just rely upon native Guix configuration. I love it.
I do still run MicroOS on all of my servers because it “just works” and I think transactional systems are great for servers. Recently, however, I’ve been thinking about trying out NixOS/Guix System as my server OS of choice, but we’ll see how that goes.
If you’re willing to put in the time, I think you’ll love NixOS.
Edit: Nix/Guix are also transactional.
So I made the jump to Linux a few weeks ago - I used to use it a lot in the 90s but I’ve forgotten pretty much everything so I listened to the general advice and went with mint. I’d recommended it. So far it’s been great, had anticipated issues with my drivers but nothing I couldn’t sort out in the GUI. There are distro options out there that will give you fewer issues - but if you like problem solving and wanted to challenge yourself, enjoy!
I’ve been loving Mint; the one thing I missed was WoW Classic but I finally found out how to get it to run under Steam and it’s been relatively great! <3
Sometimes takes a bit of fiddling but when you get it done it is bliss!
no “ultimate distro”, but i do wish there was a bigger culture of “no regressions for users”
Plasma 6 has been a series of regressions for me, such that i find my computer a little less functional almost every time i update.
That said i still like it miles better than mac or Windows, which are even worse about this
but i do wish there was a bigger culture of “no regressions for users”
Isn’t that basically Cinnamon, Mate, Xfce (and most other DEs not named COSMIC, GNOME or KDE Plasma)?
except xfce, those are both GNOME forks. Maybe the solution is Trinity DE but for Plasma 5 (Pentarchy?)
Interesting, could you provide some examples? As far as I know they just add features?
I can’t blame the devs for not advertising regressions, but it’s not something that pointieststick’s blog tends to cover.
The most recent one from the current plasma version was the removal of tiled slideshow wallpapers. You can have a tiled wallpaper or a slideshow, but you can’t have a slideshow of tiled images any longer.
The justification was to reduce memory overhead, which i understand for all the Steam Decks running Plasma, but i’ve got RAM to spare (also xfce and GNOME do this just fine). Now i need to manually make new wallpapers
Another one is window shade. Worked in all apps up until 5.27 or one of the other very late 5 releases. Still worked in 6.0 and 6.1 in non-qt apps. Fully broke sometime before 6.2 and hasn’t been looked at since.
Scroll to change desktop was disabled around 6.3. Thankfully it wasn’t removed, but it’s annoying to have a core part of one’s workflow seemingly broken after an update
Vertical taskbars set to expand automatically would crash the “configure taskbar” interface from 6.1-6.5 for me. Thankfully this one has been fixed.
Window positions are no longer remembered after a restart or log out. Setting applications to autostart in specific locations has been broken for me for a while.
I can probably come up with a couple more but i’m sure you get the picture. In each case the breakage was known before the actual release, and in each case it was decided to proceed anyway.
Don’t get me wrong. Plasma is the best desktop available IMO. I’m just disappointed any time it regresses at all.
Thanks for your very detailed explanation. That seems annoying for sure. Your used features might be niche (I’m not even sure they are) but it is always very annoying when they remove something you use daily.
Maybe extensions might help?
I haven’t found the right extensions yet but hopefully someday
NixOS paired with an LLM gives you a customized PC that won’t change. There isn’t a better option for longevity + hands off user experience than NixOS. The only downside is the big initial time investment.
True, but isn’t that a risk too? LLM’s can be powerful but also produce garbage sometimes. Especially with niche stuff?
It depends on how you use the LLM and I personally think it helped me learn NixOS/Nix/Flakes much faster than without it. You can choose to not use LLMs if you’re worried though.
First of all U don’t need to reinstall anything switch to tty firstly and find out what wrong happened second u can boot in usual live cachyos iso chroot in ur main system and reinstall all packages of system it might help but better firsrly understand what caused this
That’s true yeah. I did get a bit fed up that something like this happened again. But the nice thing about Linux is for sure that (almost) always anything can be fixed.










