I have been distro hopping for about 2 weeks now, there’s always something that doesn’t work. I thought I would stick with Debian and now I haven’t been able to make my printer work in it, I think I tried in another distro and it just worked out of the box, but there’s always something that’s broken in every distro.

I’m sorry I’m just venting, do you people think Ubuntu will work for me? I think I will try it next.

  • Nisaea@lemmy.sdf.org
    1·
    1 year ago

    I daily drive endeavour and love it to bits but let’s not recommend it to someone who wants an OS with no fuss. It WILL break and require experience to fix. Remember the grub update fiasco?

      • Nisaea@lemmy.sdf.org
        1·
        11 months ago

        https://endeavouros.com/news/full-transparency-on-the-grub-issue/

        A LOT of people’s PCs were bricked, including mine. No boot, just blank screen with blinking cursor. Thankfully Endeavour’s team was quick to react (quicker than Arch, as it happens) and published a full tutorial on how to chroot into your system and downgrade grub, but that already required a good level of knowledge and confidence in the Linux system as none of this was trivial, or intuitive for any stretch of the imagination. I woudl imagine most affected EndeavourOS users who were new-ish to Linux threw the towel that day. Wouldn’t blame them, it was jarring even for me, and it wasn’t my first chroot.

        • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍
          1·
          11 months ago

          That sounds stressfull! It’d put me off a distro, too. I had something similar happen in the early days of Gentoo - multiple times. Those trials by fire did teach me a lot, and I’m now consequently far more sanguine about the boot process, and thank god these days we have smart phones as mini-backup computers to search for solutions! Still, we’re in a time when PCs are not as indispensible, and having one down for a couple days can be a minor disaster.

          Rolling updates or no, I rarely -Syu on my desktop more than once a week, and most of my machines get that TLC more like monthly. And sometimes I’ll hold out packages that require rebooting, because FTN. It probably contributes to the fact I’ve avoided these types of dramas --statistically.

          • Nisaea@lemmy.sdf.org
            2·
            11 months ago

            Yeop, you can say that again. Can’t read the Arch wiki on a Nokia 3310 for sure lol

            Tbh I’m not too careful about updates, I have regular backups and grub exploding wasn’t enough to stop me, so eeeeh, if something really goes awfully wrong I have enough free time to deal with it and use it as a learning experience. I know I should be smarter about them like you are, but on my personal computer I just cannot be asked. ^^

            • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍
              2·
              11 months ago

              I know I should be smarter about them like you are

              TIL being lazy is “smart”.

              Nokia 3310!! Those were the days. When you had drive over to your hosting provider (some guy’s garage, who was paying for a T1) so you could sit at your server (a tower you’d built) to fix something that an upgrade had broken. Those experiences with dependency hell put me off Redhat forever.

                • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍
                  1·
                  11 months ago

                  Are you updating with eos-update, or yay? TBH, I only use yay, or pacman. I don’t imagine it makes any difference, but… IDK. I happened to upgrade and reboot two EOS machine yesterday, with again no issues. Are you running an NVidia card? I’m an Radeon guy, won’t touch NVidia, myself. How about Wayland? I’ve alwayw found Wayland to be super flakey, which keeps me on X.

                  I dunno. I wonder why you’re having so many issues, while for me EOS has just been Arch with an easier install.

                  • Nisaea@lemmy.sdf.org
                    1·
                    11 months ago

                    Mostly using eos-update by clicking on the notification, unless I’m on a terminal where I still have the yay reflex from arch. I should remember to use eos-update though, I do appreciate the extra housekeeping.

                    Nop, I avoid nvidia as much as I can as well, I already can’t avoid it at work, too much driver drama. Ryzen and radeon it is, with (almost) no fuss.

                    Also mostly using wayland, it works well even on KDE, but got Xorg around just in case, and I’ve had the occasional issue on both. That being said, it’s plymouth that blows up, long before the graphical session is opened, so that shouldn’t have an influence either.

                    Maybe I’m just a black cat, and/or maybe it just comes with the territory when you stay long enough on a bleeding-edge-use-at-your-own-risk kinda distro and update almost every day. Something’s bound to go wrong eventually. Which, has also “been Arch with an easier install” for me, tbf.

                    Gonna investigate a bit more today, couldn’t be asked yesterday. But if you’re curious I can keep you updated when I find a fix. :)

                    Edit: Found the solution by essentially doing the same thing the folks on reddit did with nvidia by enabling early KMS start, and learning quite a bit along the way. Apparently it’s now required by Plymouth and my system didn’t get the memo? Or something? Eh it works.