It usually is this simple for any distro anymore. My advice is mostly tailored to worst-case scenarios so that people don’t get overly pissy when things don’t Just Work™

There’s nothing I can say to convince you Ubuntu is sucky if you don’t personally experience problems with it/have the occasional “I wish I could do this, but I guess it’s not possible” thoughts—spoiler: it’s usually possible, just not with that distro; this is true for all distros though, there will always be things they cannot do that others can.

That being said, my biggest gripe with Ubuntu, besides canonical’s geologic-paced attempts to make it profit-driven (which was what I was thinking of when I mentioned user-friendliness), is Snaps. I understand the motivation behind them, but the implementation was just sucky for many nitpicky reasons that I don’t really care to enumerate rn.

I also just don’t see much value in downstream for my needs. I can basically turn Debian into a Ubuntu clone if I want to, and my packages will still largely be supported by upstream maintainers. For bespoke distros it makes sense, but those are usually ill-maintained or hobby projects that update at glacial speeds.

I’m not saying that Debian >>>>> Ubuntu. It’s better just enough that I’d recommend Debian before I would recommend Ubuntu.

I had very few issues with a GTX 970 and i7-4790k. The only issues I hear about with either any more is the linux kernel not supporting some of the features of newer GPUs (e.g. I know ray-tracing was a pain-point at one point).

I don’t like recommending distros based on such a general use case, mainly because every distro can be tweaked and configured to exactly what you want. Instead, you should research the different mainline distros that have been around for decades—Arch, Debian, Fedora, Gentoo, Guix, NixOS, OpenSuse, Slackware—and see what they’re about, what sets them apart from others, what the maintainers’ philosophies are, and what kind of package management system they work with. Once one sounds better than the others, look into it and try it out.

#Dos and Don’ts:

Don’t try a niche distro. They are harder to troubleshoot and less likely to be actively maintained.

Don’t use Ubuntu. It’s just a suckier version of Debian. It used to be user-friendly Debian, but now Debian is more user-friendly than it.

Don’t dual-boot with windows. This just solidifies your reliance on windows, especially if you’re the type to give up on problem-solving issues that you didn’t have in Windows. It also can cause issues with making Linux unbootable.

Do try a live usb with persistence before you commit entirely. It’s not exactly the same as a complete install, but it’s close enough to let you know how the OS feels and what hardware will or won’t work with it. Some people say try a VM first, but that won’t have direct hardware access.

Do problem solve the little things. Anything that irks you or bothers you or just slows down your workflow. It doesn’t have to be an actual bug or glitch, just anything that could be better. This not only solidifies the feeling of ownership over your OS—you no longer have to settle for anyone else’s lousy design choices—it teaches you the resources for troubleshooting larger issues.

Do plan around things not being plug and play at first. Want to test if a game runs on Linux? Great, set aside a couple of hours beforehand: first to install steam and set it up, then to figure out Proton, then to troubleshoot the game not even booting up, then to fix any glitches or whatnot, then to get your controller working. This won’t always be the case, but it will irk you a lot less when it is if you expect it. The more you make time for solving these issues now, the less time they’ll take up in the future (either they’ll be gone, or you’ll immediately know how to fix them, or your troubleshooting will be more streamlined).

Do set aside time to learn about Linux “under the hood.” You don’t have to become a computer scientist, but it will save you a lot of headaches, show you cool things you can do, and make your computer a smoother experience. It especially helps if you take the time to learn as they come up: e.g. installer asks you what “bootloader” you want, but you’re not sure what that is, what it does, or why it’s necessary? Now’s the best time to take a little learning detour.

Do ask questions on forums.

Don’t listen to the people who shame you for asking.

Do listen to the people who try to show you a better way of doing things, even if it’s not your way.

Yeah, that was warranted. I was being hostile, which is why i deleted the comment immediately after posting it

Removed by mod

Tried flatpak steam as well as valve’s installer script; nada.

I don’t generally do flatpaks, I just tried it to see if it would remove the issue

I’ll give it a shot next time I have some time, thank you!

deleted by creator

deleted by creator

Tried with root and user perms for the drive, tried with 777 on the folder and whatever permissions steam uses when it creates the folder. The drive is ext4 and mounts fine.

It doesn’t matter where or how I mount the drive, the problem isn’t the drive; idk how I could have made that clearer.

What does any of this have to do with KDE, Gnome, or nautilus?

The problem only happens under KDE and Gnome on Wayland; the nautilus thing was just a curiosity. Did you read my comment?

On KDE I couldn’t get Steam to put my game library on my second harddrive. It would open up the file finder, then simply ignore whatever folder I picked (regardless of drive and folder permissions). I was able to recreate the issue on Gnome under wayland, but X11 works fine. I even tried making a symlink to the other drive in my home directory, no dice. Tried flatpak steam as well as valve’s installer script; nada.

Interestingly, it seems that the “pick a folder” button in Steam opens up a contextual file search window in X, but just a regular nautilus instance in Wayland. I’d say that this is the problem (the regular nautilus/dolphin instance not reporting back to Steam what folder I selected), but it works for moving to different directories, just not drives (in both DEs). Same thing happened on Fedora, so it’s not just “Debian is too outdated.”

But let’s be serious, if I wanted to spend a lot of time tweaking and tuning my graphical environment to be exactly what I want, I’m not settling for Gnome nor KDE. I’m not gonna go with Cinnamon, XFCE, LXQt, LMDE, MATE, nor any ecosystem. I’m going with a window manager and mixing and matching every single program/element myself.

I use i3 on my laptops. I would use Sway (because I don’t have to care about Steam), but for some reason it’s like 5x as resource hungry on these machines (constant freezes and stuttering).

But if I’m not able to update constantly, how else will I get the dopamine hits from watching the numbers go up?

I dont want to wait a year to update my apps

Why? Are they not working as-is?

Debian generally doesn’t use PPAs, that’s an Ubuntu thing. What’s your beef with apt?

so I enabled the boot menu in the VM settings, entered it and reset the secure boot settings.

In BIOS/UEFI? What settings does this affect/what changes does this make?

If it’s your computer that you bought and legally own, tell them where they can install their Winblows 11. (The nice way to say this is to tell them to requisition you a computer or think of an alternative, because you are not going to use a personal device for company business anyway)

If it’s their computer that they own, grin and bare it.

Sorry for the delay, I’m a check-the-feed-once-a-week type lemming. I love computers, and I admire anyone who also wants to learn; I’m by no means an expert, but I am happy to share what I know.

A distro is a whole OS. An Operating System, as the name implies, is the whole system of software that makes a computer function and interactive (take input from a user, and respond appropriately). This may software definitely includes a Kernel (more on that later), but may also include things like a Display Server (software that acts as an intermediary between gui software and the display/screen), a Desktop Environment (a subsystem of related softwares that handle things like window styles, layouts, and icons), or even utilities (programs that you use to modify the behavior of other programs/processes).

In OSes, there is a fuzzy boundary between programs the user runs, and the low-level processes that run on hardware. This boundary separates “User Space” – programs and processes that run on behalf of the user – from “Kernel Space” – programs and processes that handle the hardware the machine is run on. Where most programs that you interact with are User Space – such as web browsers, video games, multimedia programs, or even most command-line programs – Kernel Space programs are ones that perform tasks like determining how memory is managed, or what processes are running during any given CPU cycle. The Kernel is the set of software that is reponsible for all this “behind the scenes” computer management. This means that the programs don’t have to be written to determine the specifics of the hardware they’re running on, it means that each program you run is much less likely to crash your PC, and it means that it’s a lot harder for malicious software to do serious damage to your PC or OS or other programs.

So that’s the Cliff’s Notes, now the ELI5 analogy version: an Operating System is like a grocery store. The Desktop Environment are all the visual elements that go into the experience, stuff like branding, signs, employee uniforms, displays, even the way the shelves are laid out. The customers are the userspace programs, and that means the employees (and the automated systems that help run the store) are the Kernel. Because the relationship between the customers and employees mostly revolves around the merchandise being sold, the merchandise will be analogous to the computer’s physical resources.

A customer can come in, select what goods they want, and check out, but they can’t stock the shelves themselves, nor order something that isn’t stocked, nor adjust prices, nor open the store if it’s closed. To do any of that, they need to ask an employee to perform those actions, and find a way to deal with it if the employee won’t or can’t. This also means the employees are responsible for opening the store, getting everything ready for the customers, cleaning up after the customers, and locking up the store after everyone’s left. This makes it easy for the customers, because they don’t have to bother with all the work that goes into shipping, pricing, stocking, theft, etc., nor do they have to worry about dealing with every possible type of shampoo they might come across depending on which grocery store they go to.

Also - I have Linux mint - does that tell you what 3 I have and if not how can I find out?

I can figure out 2 of the 3. Linux Mint is the distro / OS, and it runs on the Linux kernel. This is why distros like Arch and Debian and Linux Mint and Nix all get lumped together under the “Linux” label: they all run on the same kernel (and follow the same standards of OS design known as POSIX).

The Desktop Environment (DE) you have depends on which ISO you (or your friend) downloaded from the website, the editions are named by the DE–e.g., if you installed Cinnamon Edition, then Cinnamon is your DE. The other easiest way to tell is to run the terminal command inxi -S – and remember to check the man page for it (man inxi, or online) before running random commands from the internet if you don’t know what they do – and then checking what it says under the section labeled "Desktop: "

I’m going to comment again, not to be an asshole, but because this is an entirelt separate stream of thoughts from my previous comment:

‘GUI/UX for everything, absolutely no CLI’ approach

That’s not a distro thing, it’s a Desktop Environment thing. I personally use GNOME on my daily driver, but I’ve also used Xfce and MATE and gotten away with those. I’d say that GNOME is probably the most “idiot proof,” which is why I use it, but YMMV.

Linux “requiring the CLI” hasn’t been true for quite a few years now, it just has stuck around for a couple of reasons (imo):

1. Tutorials/guides/advice about Linux tends to focus on the CLI because it’s easier to figure out someone’s OS and have them copy-paste a command, than to find out the specifics of their graphical setup and walk them through every window and button press.

2. New users need to know and understand the difference between Kernel, OS, and Desktop Environment to find the answers they’re looking for.

If you tell Grandma that you installed Linux for her, the first time she tries to figure it out herself, she’s gonna search “how to change volume in Linux” on Google, and she’s going to be bombarded with a thousand answers all saying something different, most telling her to install programs, and most telling her to use the command line. Because Linux is not an operating system, it’s a family of dozens of operating systems that can each be configured thousands of different ways.

If you tell her “I installed Fedora,” she’s going to run into the same issue, but on a lesser scale. At least there’s only a few hundred different ways on a per-distro basis.

If you tell her “I installed GNOME,” she will look up “how to change volume in GNOME,” and find her answer. But now you need to explain to her the difference between the three, and when to include that information in her searches, and she will ask “why could I just say ‘how to X in Windows?’ and didn’t have to memorize 3 different names for the same thing that all give me different answers???”

And yes, your grandma will just call you to ask anyway, but what about when it’s your friend trying to figure it out at 3 am and he can’t get ahold of you?

Meanwhile, the terminal is (more or less) distro-/DE-agnostic. So their options are to learn more about how is Opperating System formed than they’ll realistically ever need to know, or use the reviled terminal. Such is the plight of DIY OSes.