Conty VS AppImageLauncher

For the glory of mankind he edited his post saying that running Steam through conty (https://github.com/Kron4ek/Conty) fixed his problem with EAC enabled games.

Have you tried using: Flatpak (use flatseal for other library locations), Conty (use HOME_DIR in case you want to separate it from host's .steam folder), or Distrobox (use Bazzite-Arch image for quick setup)

nah, there is conty to save the day of not dealing with i386

Or go the https://github.com/Kron4ek/Conty way

These ideas I'm toying with also is what made me request the non-image option with Conty here (https://github.com/Kron4ek/Conty/issues/77) where u/Kron4ek speedily patched an option to do so (ty!). Though I'm still pondering what I'm trying to do and if it would make sense with Conty.

I'd imagine the sandbox options are bubblewrap presets, though -- you'd probably want to look around conty-start.sh for more details or ask in the GitHub Discussion.

Have you tried Conty? The best way I could describe it is the combination of distrobox and AppImage. You basically build a single binary (or use the pre-built one the dev made) containing a minimal Arch install and any other packages you listed in the create-arch-bootstrap.sh file.

Do note that with Nobara having Fedora base, some stuff might not have a Flatpak/AppImage or RPM for you to install easily unlike on Debian/Ubuntu-based (tho PikaOS is Nobara re-implemented under Ubuntu-base, but I haven't tested it). Distrobox and Conty may help you with that, but if you were fine with Steam Deck's limitation, you should be alright under Fedora-based distro.

It's why I usually just run Bottles in Conty. nix-unstable also have the latest Bottles builds, though I haven't tested those yet. I don't think the default permissions is a big problem though, just something to note if you store your games outside of areas it has permissions for by default.

Conty https://github.com/Kron4ek/Conty looks interesting, but also relies on an image, here squashfs. Mentioned in this comment along with some more options: https://www.reddit.com/r/linux/comments/xq09nf/comment/iqdigoe/?utm_source=reddit&utm_medium=web2x&context=3

Every file that you want to execute has to be in your environment PATH. I would also advise to put symlinks and personal executables in ~/.local/bin and put that to your path. Since your user has ownership over that directory, you won't have any probs with permissions that may or may not occur at all. Since we're talking about AppImage files, you might also want to take a look at AppImageLauncher which does a pretty good job at creating entries for your Desktop Menu for the AppImage files that you install to your system.

I think it's safe to install it directly as it stores everything in a single directory. For AppImages there is also AppImagePool + AppImageLauncher (can be installed rootless, useful for better integration of appimages).

This reminds me of a prettier version of AppImageLauncher. Is there also an "Uninstall" option in the right-click menu of the app launcher?

I'm using AppImageLauncher on Fedora.

"... I recall that this was related to an issue with most Electron apps, wherein the AppImage cannot be integrated with the desktop or the favourites bar. So far we've found that the AppImageLauncher (https://github.com/TheAssassin/AppImageLauncher) helps with getting around this!