boredsquirrel

@boredsquirrel@slrpnk.net

This profile is from a federated server and may be incomplete. View on remote instance

boredsquirrel ,

Plasma 5 to 6 with a long used setup went perfectly.

Fedora Atomic Plasma Workstation? I am in!

boredsquirrel ,

You can mask flatpaks to not update. Likely also rollback

boredsquirrel ,

No f40 version? Is there a spec file? Should be possible on COPR

boredsquirrel ,

Yeah nearly all Fedora KDE issues are direct upstream Plasma issues. And not too many, tried Plasma 6 on Kinoite Rawhide for a while and reported a lot of them.

You can do the same with COSMIC and help make their release better!

boredsquirrel ,

So those are either random 3rd party problems (please contact the COPR maintainers, there is Discourse integration) or direct Plasma issues :D

I was also a bit hesitant to already upgrade, as I tried Plasma 6 before and it wasnt perfectly stable, but I actually havent had any issues yet.

3rd party stuff of course

  • minimal desktop indicator
  • video lockscreen (ironically had a Qt5 bug with seemless playback that may now be fixed)

Some extensions have alternatives like Thermal Monitor, but upgrading was unintuitive. It needed removing and adding back.

boredsquirrel ,

There is an officially supported Flatpak

I would 100% use that. Snap on Fedora is likely not sandboxed at all, as it relies on Apparmor, and also not really that well maintained as nobody cares.

boredsquirrel ,

Same, still have Kinoite 39 pinned to be safe (even though I imagine rolling back would cause tons of broken dotfiles), but didnt need that.

Dotfiles are really the issue.

boredsquirrel , (edited )

No they just package the exact same versions, but differently. It uses rpm-ostree which is like Git but for operating systems (binaries).

A quick tour through Atomic Fedora

It relies on a main image, which could just be used like that. This is a minimal Fedora install, containing everything thats needed and nothing more.

You would then install apps via Flatpak, Appimage, binaries, Toolbox etc.

Or you can layer RPM packages, and you can install everything as on normal fedora. This will make updates a bit slower but is usually needed for small things like a different shell.

These packages will be kept updated in parallel to the OS. The OS is always 100% what Fedora ships, while the RPMs come from all the repos you can imagine, COPR, rpmfusion etc.

Rpm-ostree pulls down the update and the packages are added to that. But instead of modifying the current OS, it clones it, using the current one, and the differences (updates) that are downloaded.

This new image is now either complete, or gets the wanted RPMs added or removed. The new image is then set as new boot target.

You can use your system how long you want, but when you reboot (and this takes not any longer than a regular reboot) you will boot into the new version.

If something broke, you always have the last system kept. You can increase that number, so only the x-th last image gets automatically deleted. And you can manually sudo ostree admim pin 0 the current system, if you know it works well and you have for example a driver update, or a big system update, and want to be sure you will have this as backup.

You can also rebase, which means your system will now mirror a different repo of theirs. For example from Silverblue (GNOME) to Kinoite (KDE). This will change everything so that you now 100% have the packages of the new repo, failsafe.

If it would fail, the update would cancel and you dont get one.

So remember:

  • the system by default is 100% the one that Fedora ships. No manual upgrades, no strange "cant reproduce on my system" conflicts, nothing.
  • you can still install all RPMs you want
  • you can remove RPMs from the system
  • you can reset the system again to be 100% upstream
  • you can rebase to a different variant. Like Fedora to uBlue, including NVidia drivers and some packages. Or advanced images like Bluefin/Aurora, or Secureblue variants
  • updates either work 100% or fail
  • you will always have a fallback system (not only a kernel, an entire system) and you can keep as many as you want, forever

So basically: rpm-ostree gives you the needed control to have a stable OS.

But still not everything is "immutable" /managed with rpm-ostree. Your entire /var is mutable, and /etc and /home are symlinks from that. This means you can configure and break what you want, which can also be problematic.

Note though, that the vanilla /etc files are stored in /usr/etc, so you can restore them. Make sure to exclude crypttab, fstab and a few more!

boredsquirrel ,

Use the Atomic variants from uBlue! This will make sure stuff like that happens on their servers, they fix it once and the users always get working updates. (Maybe with a day delay in cases like this)

boredsquirrel ,

Source

Enabling Tap-to-click in SDDM Wayland (Fedora 40 Sway)? (SOLVED)

Essentially as the title says, I'm running SDDM with the Wayland backend on Fedora 40 Sway edition and I want to enable tap-to-click for my touchpad. Any ideas on how I can do that? I tried doing it in the xorf config but then I realised the x server isn't even installed so SDDM is actually running on Wayland, and I don't know...

boredsquirrel ,

Try this, may be an AI hallucination

mkdir /etc/sddm.conf.d
cat > /etc/sddm.conf.d/custom.conf <<EOF
[Input]
EnableTap=true
EOF

In general avoid overwriting default files, as this .conf.d seems to be pretty standard. Your distro will handle the default .conf but may stop when you changed it manually.

boredsquirrel ,

Yes GPT 3, it gave me nothing with X11 at least. If SDDM had some abstraction configs for the compositors, that would work.

Did you restart SDDM / the system? And did you try adding that directly to the main file?

boredsquirrel ,

Fedora is not stable but very well tested it seems.

And GNOME (the default, I guess?) Is also just really well tested

boredsquirrel ,

If they are anti X why dont they use Wayland then.

boredsquirrel ,

No shit I think flashing ISOs is now fine that we have Impression, Fedora Media writer und the KDE Usb flash tool.

But how the hell do you install Tails? May have to do that again, but last times it was never bootable.

boredsquirrel ,

Try "keyboard shortcuts" and select some action, then use the button as input, or look in the mouse settings.

Is there a "nothing" action? May be useful here.

boredsquirrel , (edited )

Fedora Kinoite or Silverblue as base. They are so stable, very nice to know they will not break. You may want universal blue.

GNOME has some form of parental control too but no idea. I would trust it way more than ElementaryOS, as it is one of the 2 main Linux Desktops.

GNOME is also stupid simple to use.

It may break KDE apps themes, and KDE has tons of nice learning apps. So I dont know about GNOME.

Education:

Educational Games:

Random harmless games

Easy tools for learning stuff

boredsquirrel ,

If you dont have an admin account you cannot break the core system anyways.

I agree that rpm-ostree based distros are awesome here, but Linux Desktops are not made to be locked down.

boredsquirrel ,

What version of doas though? Opendoas is hardly maintained.

boredsquirrel ,

I didnt understand that sentence. Is that what you meant?

Among other things, Debian wanted to integrate a part of the systemd tools into openssh, which almost led to a worldwide catastrophe

xz is not part of systemd or openssh afaik.

boredsquirrel ,

Ok true, it was a systemd dependent issue. But it only makes sense to have those notifications. The problem is dependency on small hardly maintained products, which systemd will improve by centralizing it.

boredsquirrel ,

I dont know but for sure has pros and cons

boredsquirrel ,

You are talking about Debian holding back random packages for stability. This is of course not very cool but it needs to be tested.

I am very much in favor of isolate app environments controlled by upstream devs, containerized and with a permission system. The system is made by the distro, and can be stable and very tested, and the apps are simply isolated and made by upstream.

There is no xscreensaver on Wayland and I think this will not come back?

boredsquirrel ,

Pretty damn cool! Using it since a while.

Have to say the UI is really strange though. Tbh I find all players kinda strange, G4Music is likely the best.

I just want

  • folder view, playlists, artists, albums, all
  • play one of these (not create a playlist and then play that)
  • save and sync playlists from and to .m3u files

Still struggling to get synced playlists between android (anrimians music player) and Linux. Anyone got tips?

boredsquirrel , (edited )

Why would you do that, there is absolutely no reason. Fedora only supports upgrading one version up. oops its 2

Stay on the old stable if you like, but then switch to the latest? Why?

boredsquirrel OP ,

Hahaha I also dont think we need more of them. But improving the already existing ones for sure is good!

boredsquirrel OP ,

Or cosmic-comp, based on her work on smithay, also fully working!

boredsquirrel , (edited )

No, KDE is just as well supported on Fedora, dont worry. I use it daily.

I also highly recommend using Fedora Kinoite from https://ublue.it

It is way more reliable, you cannot imagine how much. It is the best distribution model in my experience, you never have to worry about updates breaking anything, and you can always go back to vanilla.

boredsquirrel ,

If you like and trust Homebrew for packages, yes.

I have to try it, am kinda suspicious but I guess it is a good distribution method?

boredsquirrel ,

I dont get why they push Ubuntu so much. I use a Fedora toolbox which works great... apart from the fact that there is no damn upgrade! So only rawhide possible, lol.

Rebasing and rpm-ostree are truly beautiful. And adapting to it, for example packaging stuff written to /usr into an RPM, is interesting.

I have at least 2 use cases (placing different SDDM launch scripts, SDDM themes and something else) that need to be written to the immutable directory.

I think documenting how to package "put script abc to /usr/foo/bar" into an RPM, or even automate it, will be lit. Will try to figure that out when I have time.

Lunarequest did this with sddm2rpm but only for that job.

boredsquirrel ,

Yes for sure.

  • Fedora packagers do the heavy lifting of shipping the packages
  • ostree pulls in and versions the OCI images
  • rpm-ostree layers RPMs onto the base image but on their side, so they can install exactly what they need. Its all CI/CD Github actions
  • they include all the files needed for a perfect experience
  • they have yafti and ublue-update, which fill the gaps
  • on your machine, rpm-ostree just needs to update
boredsquirrel ,

Proxmox is an entire distro just for running virtual machines, with a web UI. Virt-manager is a program you install on a normal machine

boredsquirrel ,

Bare metal is "kernel running on hardware" I think. KVM is a kernel feature, so the virtualization is done in kernel space (?) and on the hardware.

boredsquirrel ,

TL;DR: use what is in the kernel, without strange out of tree kernel modules like for VirtualBox, and use KVM, i.e. on fedora virt-manager qemu qemu-kvm

boredsquirrel ,

Yes it is, I dont know the technical details but KDE tends to freeze a lot. I dont know if it is impossible? Why cant apps just have a UI that always works, and the process may freeze doesnt matter?

boredsquirrel ,

Really interesting but I still dont get the title, you might rename it to "TL;DR about the NixOS drama" or something?

Discover - possible to limit download speed?

Hi, sadly I have a very limited internet connection (10 Mbit). When I'm watching a video and then install something in Discover, it takes almost all the bandwidth and the video begins to stutter & buffer. Somebody knows if there's a way to limit the download speed for discover - preferably without installing additional software?

boredsquirrel ,

Yeah but then it is not the only solution.

boredsquirrel OP ,

Hahaha this. If you are paying them, this is not a community.

boredsquirrel OP ,

Yes but you can add all buttons.

boredsquirrel ,

No the implementations are per-compositor. The fact that this worked on X is due to.XOrg being a huge blob that every window manager relied on.

Look for the command in Mutter (GNOME), Kwin (KDE), or whatever DE you use.

boredsquirrel ,

Its how Linux works lol. I mean there are tons of things per compositor.

The protocols are way cleaner and less, so it is easier for Distros to just write their own.

But for sure it is annoying that everyone wants to do their own. But that is not a Wayland problem, just nobody wanted to mess with XOrg.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • All magazines