Additionally you could move the git folder to the trash folder. I think it’s usually located at $HOME/.local/share/trash/files/

Moving something to the trash files folder isn’t the correct way to trash it, since the Trash specification requires storing some metadata for each trash item.

You should use eg. trash-cli instead.

bwrap wants to have a word with you

they are extra heavy in disk space

While they use more disk space than most native packages, this point is often exaggerated. Flatpak uses deduplication and shared runtimes if multiple apps use the same runtime.

Common libraries like OpenSSL are usually bundled in runtimes. So if my application uses e.g. org.gnome.Platform, I don’t have to update my application if there is a fix in a library of that runtime, I just need to update the runtime.

The runtime is also shared by all applications that use this runtime.

The steam flatpak can’t install udev rules. It works if you install a packacke such as steam-devices on your host system. See https://github.com/flathub/com.valvesoftware.Steam/wiki#my-controller-isnt-being-detected

This comment didn’t age well.

What should be shown if there is currently no playback?

The documentation says:

Waydroid uses Linux namespaces (user, pid, uts, net, mount, ipc) to run a full Android system in a container and provide Android applications on any GNU/Linux-based platform.

To my understanding this isn’t even emulation but regular container technology.

Will have to switch back to X.Org until this is fixed by the Wayland/XWayland developers

This isn’t the responsibility of “wayland developers”. The developers of an application need to adapt to the new API.

Wayland monolith

There seems to be misunderstanding about what Wayland is.

Wayland is set of protocols. They are implemented by wayland servers (compositors) and wayland clients (applications) themselves. There is no single “wayland binary” like in the X11 days. Servers or clients may choose to implement or not implement a specific protocol.

You don’t even need to create aliases yourself. Flatpak creates wrapper scripts for every app that you install. Just symlink them into your PATH.

ln -s /var/lib/flatpak/exports/bin/org.example.CliTool ~/.local/bin/cli-tool

or if you are using a user remote

ln -s ~/.local/share/flatpak/exports/bin/org.example.CliTool ~/.local/bin/cli-tool

(Note: some lemmy clients render the the tilde in code blocks incorrectly)

Snaps are just as “open source” as “Office Open XML” (.docx, .pptx etc.) are open file formats.

If there isn’t a fully open source software stack, it isn’t really open source.

GNOME 46 has experimental VRR support too

GNOME got proper Wireguard support in version 44, unfortunately Debian stable ships an outdated version (43).

Cosmic is a desktop environment, not a distro. So Pop!OS will keep using deb packages and something like a Fedora Cosmic Spin will use rpm packages.

Are you sure this is the only error that you get?

Make sure to check if there is a message Attempt to free invalid pointer. This is a known problem for source games: [Linux] Failure to start with tcmalloc “Attempt to free invalid pointer” and lavapipe built against llvm 16 and workarounds are available.

Tbe documentaion is a good starting point.

https://docs.flatpak.org

https://docs.flathub.org

This is exactly what this change is about. Most blurry apps are blurry because they don’t support Wayland (yet/by default) and are running using XWayland.

The only Wayland native software where I had problems with fractional scaling is Qt WebEngine which doesn’t handle scaling correctly.

The worst part about signing up somewhere is the amount of email spam that will land in you inbox. I don’t know about their specific configuration, but by default Discourse (the forum software they use) sends weekly “digest emails” if you haven’t visited the site for a week. So make sure to turn them off.

There was an issue in the past where the regular mesa-* packages and the mesa-*-freeworld were out of sync which resulted in no longer working DEs for many people if they updated at the wrong time.

Is this still an issue?

(I went back to the regular drivers since I mostly use VP8/9 anyway)