Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AppImage to distribute games #4837

Open
probonopd opened this issue Jan 29, 2017 · 8 comments

Comments

Projects
None yet
7 participants
@probonopd
Copy link

commented Jan 29, 2017

Could games through steam be distributed as AppImages?

This would have, among others, these advantages:

  • Works for most Linux distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)
  • One app = one file = super simple for users: just download one AppImage file, make it executable, and run
  • No unpacking or installation necessary
  • No root needed
  • No system libraries changed
  • Just one format for all major distributions
  • Works out of the box, no installation of runtimes needed
  • Optional(!) desktop integration with appimaged
  • Binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
  • Can GPG2-sign your AppImages (inside the file)
@Sunderland93

This comment has been minimized.

Copy link

commented May 25, 2017

It's better to see Steam Runtime as Appimage, but not games.

@probonopd

This comment has been minimized.

Copy link
Author

commented May 25, 2017

Can whoever votes this down give a reason please? And yes, it should entirely be doable to distribute the Steam runtime as an AppImage. In fact I have tried but the runtime is so convoluted that I'd need someone from Steam to collaborate on this to get it done.

@Sunderland93

This comment has been minimized.

Copy link

commented May 25, 2017

Can whoever votes this down give a reason please?

Because Steam games depends on Steam as DRM-service. It's not DRM-free games, like in GOG. And Appimage has make no sense.

Works for most Linux distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)

It's already works on any distro which running Steam

One app = one file = super simple for users: just download one AppImage file, make it executable, and run

Not needed.

No unpacking or installation necessary

Steam games simply download and ready to work

No root needed

Steam not needs root, all Steam games as well.

Binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate

Not needed, because Steam updates also work

@probonopd

This comment has been minimized.

Copy link
Author

commented May 25, 2017

It's already works on any distro which running Steam

Yes, but only on those. And the Steam client needs to be installed first.

One app = one file = super simple for users: just download one AppImage file, make it executable, and run
Not needed.

...for you. I just like the convenience of being able to copy one single file to a different machine and have it run, without needing to download or install or unpack anything again.

Steam not needs root, all Steam games as well.

Last time I checked, Steam did invoke apt commands during installation which not only clearly needs root, but also changes the libraries in the system.

Because Steam games depends on Steam as DRM-service.

Bummer.

@Sunderland93

This comment has been minimized.

Copy link

commented May 25, 2017

I just like the convenience of being able to copy one single file to a different machine and have it run, without needing to download or install or unpack anything again.

Then use GOG :) Steam client as Appimage is good idea, but Steam games as Appimages....

@jubalh

This comment has been minimized.

Copy link

commented Nov 5, 2017

It's already works on any distro which running Steam

So I run Steam on openSUSE Tumbleweed. Trying to open Magicka 2 nothing happens. No error window nothing.

So I do:

cd .local/share/Steam/steamapps/common/Magicka 2/engine
./Magicka2_x64       
./Magicka2_x64: /usr/lib64/libssl.so.1.0.0: version `OPENSSL_1.0.1' not found (required by ./Magicka2_x64)

So it needs a different version of openssl that openSUSE ships.
So much for works on any distro which running Steam :(

Having the games as AppImages would make much more sense.
No more dependencies on having the libs at the paths that they are located in in Debian.
No more dependencies on having exactly the same (old) lib installed on the system.

Then use GOG :) Steam client as Appimage is good idea, but Steam games as Appimages....

Exactly the games are the ones not working because of being built against different paths/library versions

@RafaelLinux

This comment has been minimized.

Copy link

commented Nov 14, 2018

It's already works on any distro which running Steam

So I run Steam on openSUSE Tumbleweed. Trying to open Magicka 2 nothing happens. No error window nothing.

So I do:

cd .local/share/Steam/steamapps/common/Magicka 2/engine
./Magicka2_x64       
./Magicka2_x64: /usr/lib64/libssl.so.1.0.0: version `OPENSSL_1.0.1' not found (required by ./Magicka2_x64)

So it needs a different version of openssl that openSUSE ships.
So much for works on any distro which running Steam :(

Having the games as AppImages would make much more sense.
No more dependencies on having the libs at the paths that they are located in in Debian.
No more dependencies on having exactly the same (old) lib installed on the system.

Then use GOG :) Steam client as Appimage is good idea, but Steam games as Appimages....

Exactly the games are the ones not working because of being built against different paths/library versions

I agree. Exactly the same is happening with Zero-K in OpenSUSE 15 and Steam Play (beta). I can play Zero-K with Lutris (needing previously to install mono-base, that's the truth) but I supposed that Steam will play Zero-K without any user intervention after installing it from Steam platform, but it's doesn't work. After installing it in Steam, I launch Zero-K and ... nothing happens (it seems to begin to launch and nothing happens finally). So, yes, I think AppImages could solve these problems.

@nipsy

This comment has been minimized.

Copy link

commented Jan 8, 2019

@jubalh You've probably already moved on at this point, but my report in #6014 discusses how to successfully run Magicka 2. Steam already includes most of the essential libraries needed to run a lot of the i386 and x86-64 Linux games.

But if you're going to try to run them directly yourself from the command line, you need to run them via a wrapper script which sets up the environment in which the games run for the dynamic linker to be able to find the libraries installed with the Steam client itself.

Something like this (the fix and how to run it with the Steam versions of these libraries):

ln -s ~/.steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/libssl.so.1.0.0 ~/.steam/steam/steamapps/common/Magicka\ 2/engine/libssl_conf.so
cd ~/.steam/steam/steamapps/common/Magicka\ 2/engine; ~/.steam/ubuntu12_32/steam-runtime/run.sh ./Magicka2_x64

Adjust your own Steam installation path as necessary in the above obviously.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.