I have a Mac running OS X 10.9 that I share with my wife. We each have our own accounts, and we use fast user switching, so we're both always logged on, but only one account can use the computer at a time.

When I launch GOG Galaxy, I get a dialog box that says,


Too many user sessions running

Galaxy Client does not currently support running with multiple user sessions. Please ask other users to log out of the system.

I've been disappointed in GOG before, but this is a new low. There is no way I'm going to be logging my wife out of her account just so that I can launch GG. I did throw GG in the trash, though, because that's where it belongs. IN THE TRASH.

Dear GOG: stop screwing around, and fix your crap.

I have the exact same issue on Mac. I still love GOG, but I can not use Galaxy. It just doesn't work with my Mac, which also has two user sessions.

Weird.. are you sure you just don't need to close Galaxy from you wife's account?

Not that a well-behaving application should care whether there are multiple copies of it running, even on the same user account.

Umm.. actually it's good that some programs allow only one instance.
Imagine multiple "Galaxy" trying to update the same games...ugh.
But for different users & folders that should be allowed.

Anyway, I was just suggesting a better practical alternative to logging out the wife XD

They made some questionable design choices in other areas too.

Installing the client into /Users/Shared is not what this directory is supposed to be used for. They should have installed the Galaxy.app bundle into /Applications and its supporting files into /Library instead. /Users/Shared is a shared location for users, not programs. I also noticed that everything in that directory as well as the app bundle itself were world-readable and world-writable, which means that any process and any user can see and do anything with this.

I also saw a file called ‘token.something’ in there which contained a string of characters, reminiscent of a session or authentication token (this is probably generated when you log in and used to remember you when you re-open the program). It made me very suspicious that this file was placed there in world-readable plain text. I worried that this token could be stolen and used to access my account.

There is also a daemon running with root privileges when GOG runs, which begs the question whether that is secure. It rarely necessary and a good idea to run with root privileges. The potential for vulnerabilities is a non-negligible risk.

I saw too many red flags and questionable design choices in Galaxy. On top of it, it shipped with a complete Chromium browser inside (that's what this is, a glorified browser). I cannot say whether this has changed by now, but I could not recommend this program to any Mac user because of these factors.

They could very well build a system that tells which games are "in use", and even how (ie. "playing", "installing" or "updating"), that other instances of the application can read, and then know to disable access to games when those flags are in place. It needn't be very advanced either, put a plain text file with a specific name in the game's folder containing the flag, the executable's process id, and possibly a timestamp. The application can then check if the process id is from another instance of the same application (same path to the binary but different id, though this is perhaps only possible if the two instances are running as the same user, depending on how the system is configured, you can only see your own processes), and know to not make said game available to the user while it is.

I have the same issue. Only one User is allowed to be logged into the computer. It does not matter if he uses gog client or not. Just a log in on the system is enough to block the client from starting. What the hell should this feature be ? Why my wife is not allowed to be logged into the computer even if she never used the Galaxy Client. Please fix that crappy feature.

Why I do not ever use Galaxy... Good thing it is not needed.

Complain in the Galaxy sticky thread to have a much better chance of the staff actually seeing this. Maybe make a link to this thread.

Just discovered this "feature". GOG please fix it, it is ridiculous. Thanks.

Mine does the same, but now it won't quit. I can't even force quit it!!!!! Help!

Yep, this sucks...

Still experiencing this. Please fix.

It's almost like they never heard of a lock file or file locking. Locking a file when opening the galaxy client or running a background update probably takes the same or less code than checking how many users are logged in.

1-2 lines of code is not complicated.

How has this still not been fixed? It's been literal years. Come on, folks.