Wouldn’t this be better achieved with udev rules instead of an always-running script?

I use AntiX (core) with runit, and it’s basically just an opinionated Debian with less systemd bloat (and extra packages from MXLinux repo). It works swimmingly on my laptop with an i3-4030U Lenovo Flex 2 (although I did upgrade to 16 GB of memory). It worked blazingly fast headless, but is still remarkably performant for Sway; as for not looking old/ugly, Sway is beautiful as long as you put in the time to customize it

I actually got into Sway bc of my love for i3wm, and Wayland has gotten to the point where I’m no longer seeing any benefits from sticking to Xorg (although there are probably edge cases); I predict that Wayland will be superior option for older hardware within a couple of years, unless XLibre makes some major leaps.

Are there mobile desktops for Debian?

If you just want the DE and to configure everything else yourself, you can always just install phosh or sxmo on top of a debian/raspbian installation.

Mobian/Droidian are targeted for smartphone SoCs, so they would take a lot of tinkering to get runnin on an RPi

If you want a full OS that’s already configured to be a smartphone-like device, something like Glodroid may be your best bet. They’re an infrequent updater, the only reason I mention them is because they can target Broadcom devices (like RPis)

If you don’t mind getting away from building the hardware yourself, and just want a phone that you can run linux on, FairPhone/PinePhone/Librem 5 seem to be the way to go

Aside from that, afaict you’re in for designing your own device from extant components and then crowd-funding to pay for a factory line to assemble it for you (this is essentially what the PinePhone did)

There’s probably a better way, but the way that works for me is apt show <package> and then copying everything from the Recommended section into an apt install command

Edit: people in forums are suggesting the simpler apt install --reinstall --install-recommends <pkg>.

I find this preferable because it means the recommended packages get marked as auto, which means an uninstall will automatically remove them.

On the other hand, it forces a redownload and install of <package> which might be unwanted. If you want the best of both worlds, you’re going to have to manually install the recommended packages, then also manually apt-mark auto <list of packages>—although that might make them immediately susceptible to an autoremove, so this might require some tweaking; I’ll work it out when I have time.

If you want to always install recommended packages, add APT::Install-Recommends "1"; to your apt.conf (which just includes the --install-recommends option by default, behind the scenes)

As a rule I don’t tell people to RTFM, because it has some rude dismissive connotations, although I will share when it helps me solve a problem I’ve been butting up against that would’ve been solved if I had just read the docs.

That being said, I do encourage people to read the docs, as others’ walkthroughs can be misinformational, and are usually tied to specific setups or software and hardware versions. It requires learning how to wade through a lot of information to find the info you need, but the info is usually guaranteed to be the most current and reliable.

That all being said, I’m more than happy to help when people want it.

Podcasts?

If you really want to save some space, you can save a lot by opting to use command-line programs instead of the GUIs that basically just act as front-ends for the command-line programs. E.g. most FOSS audio converters just use ffmpeg behind the scenes, so really they’re a lot of extra libraries and such just to give you a graphical means of building up the CLI command. Same goes for videos. Same for images, though a lot of those might use imagemagick instead (even though ffmpeg also does images).

That being said, I use VLC for converting videos and audio files. I honestly can’t tell the difference between uncompressed (e.g. .wav), lossless (e.g. .flac or .ape), and high-bitrate lossy like mp3 v0 or mp3 320. Heck, I can’t even tell the difference between the aforementioned and mid-bitrate lossy audio like mp3 192 or Vorbis (the .ogg format) 192.

Quality is of course dependent on how sensitive the listener’s ears are, and how quality the equipment you’re listening with is. You’ll want to run some test conversions youraelf before committing to any specific format.

If your files are already in lossy formats, then you really don’t have much choice for compression, outside of bundling them all together in a tarball and compressing them with something like gz or zstd. This is only good for storing them, if you try to listen to them, your system will have to extract them, and that either takes time before it plays, or causes stuttering while it plays.

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).