MajinBlayze [any, he/him]

A VPN is definitely an example of software you should use rpm-ostree to install.

To add some detail, anything you install in a distrobox (or other sandbox/container) can’t add kernel modules, which I think is the error you’re getting.

deleted by creator

It’s not quite that simple.

Each package can choose one from a handful of runtimes to use, each of which include common dependencies (like gnome or qt libraries), and if multiple flatpaks use the same runtime, that runtime is only downloaded once.

It is less space efficient than your typical package manager, but brings other benefits like sandboxing.

I’m not sure what the chances actually are, but that much rewriting and shuffling data, if it doesn’t immediately result in data loss it is going to put a lot of wear on your drives. If your largest drive is 8 TB, I’d look for another 8+ TB drive so that you can copy the data and then reformat. Even a slow external drive is likely to be faster than what you’re doing.

There’s plenty of rational reason to hate this video

I would say steam deck, both in actual installs and in raising awareness, but that wasn’t until 2022

Switched from the kde test repo over to baseline Tumbleweed today. It was actually smoother than I’d expected

Uninstall and reinstall the game between users…

More seriously, I think bazzite is keeping a traditional login screen instead of using the steam one, so you could have actual segregated user accounts

I’ve been running kinoite on my laptop for a short while now, and I wanted to address a few miscellaneous things.

First: I recommend trying the out of the box experience for a while before going far customizing it. For example, someone mentioned your filesystem layout with subvolumes: that’s the default in kinoite: home, var, and root are in subvolumes.

Second: Wayland either is or is about to be the default in fedora (I’m running the beta for the next version, and it’s Wayland by default). Try it and see if you have issues before trying to switch to x11.

Flatpak is your first stop for installing software on kinoite, but the fedora repo that’s configured by default is missing a lot. If shows software available that you don’t see in discover/flatpak, you need to add the flathub repo, which is easy to do, but not obvious (to me) that it wasn’t the default.

Finally, Nvidia experience might not be good ootb. You might need to take extra steps to get the proprietary Nvidia driver.

Good luck with your endeavor!

Edit: Firefox

I don’t understand why the default install of Firefox isn’t the flatpak version. Switch to the flatpak version and you won’t have to worry about codecs.

Lol, I just noticed that this thread is 3 weeks old… How is your setup working out?

sudo chown -R /path

sudo chgrp -R /path

I’m running kde6 on fedora rawhide kinoite, it’s pretty stable.

Minor point of clarification though, kinoite isn’t immutable ootb, it’s atomic (which is to say it either fully updates or doesn’t. Immutable is an experimental setting you can enable though)

You’re using flatpak, right? Flatpak uses “portals” to provide access to other parts of your system. When you open files in flatpak apps, you’ll see this folder used for those.

These shouldn’t actually take up any meaningful space, and I wouldn’t delete anything unless you’re experiencing an issue.

I would take that one step further and recommend an atomic release: like fedora silverblue or kinoite for someone new to Linux. The read only base filesystem makes the risk of breaking things basically zero.

It does make some tutorials invalid though, which can be a source of frustration.

TIL SDDM hasn’t gotten to 1.0 yet.

How long has it been the de facto default greeter for KDE Plasma?

Same time as Tumbleweed, which will probably be pretty quick after the release next week

Tbh it’s possible I messed something up, iirc the bridge network I was using wouldn’t work, and it seemed like it would only work in host mode, hence the belief that I needed to remap things. This was over a year ago, and tbh I didn’t try very hard to make it work.

Yeah, podman’s networking approach sent me back to docker as well. I have a bunch of services that don’t even expose their ports to the local network, they just connect to each other, and only the reverse proxy is exposed. Switching to podman would require me to reconfigure all my port mappings to make sure there aren’t any conflicts, and then update all the references. It’s not a ton of work, but enough to keep me on docker for the time being.

edit: It looks like podman’s networking stack has changed since I used it, so this is almost certainly wrong now

I’ve been using microos exactly because I like to tinker. Just the other day I installed plasma 6 to play around with the HDR implementation, then decided that it wasn’t worth it and rolled everything back. Worse case scenario I might have needed to reset kde configs in my home directory, but even that want necessary.

Thank you, I needed that today