It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Attempting to install Long Live the Queen on Mint resulted in a python.real: not found error on attempting to launch the game. The shortcut did nothing, while the terminal (gog-long-live-the-queen) let me know that it couldn't find a 32-bit version of python.

If you get this error, open the terminal and type in: sudo apt-get install ia32-libs

You will then be prompted for your password, and the terminal may ask you to press Y in order to allow the installation to continue. This can take some time, but this resolved the error for me.

GOG team, is there anything that can be done on your end about this via the installer, or is this a customer-end problem?
avatar
garthand: GOG team, is there anything that can be done on your end about this via the installer, or is this a customer-end problem?
What version of Mint and which installer? I tried this earlier on a nearly stock Mint 17 64-bit install with the tarball, and did not have any problems. Also, with the tarball you need to manage the dependencies manually. Use the support link to send in a ticket if you want GOG to see this.
Post edited July 27, 2014 by Gydion
avatar
garthand: GOG team, is there anything that can be done on your end about this via the installer, or is this a customer-end problem?
avatar
Gydion: What version of Mint and which installer? I tried this earlier on a nearly stock Mint 17 64-bit install with the tarball, and did not have any problems. Also, with the tarball you need to manage the dependencies manually. Use the support link to send in a ticket if you want GOG to see this.
Mint 16, which is not technically supported, (part of the reason I wanted to post this here first). My comment pertained to the installer, not the tarball.
avatar
garthand: Mint 16, which is not technically supported, (part of the reason I wanted to post this here first). My comment pertained to the installer, not the tarball.
Sounds like a bug to me. Doesn't seem like the .deb has all its dependencies set.