github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #1240] Firejail and Steam Games #846

New issue

Closed

opened 2026-05-05 06:58:01 -06:00 by gitea-mirror · 11 comments

gitea-mirror commented

2026-05-05 06:58:01 -06:00

Owner

Originally created by @Alexey2532 on GitHub (Apr 21, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1240

Hey,
i was trying to run 2 games via 2 different firejails. i got Steam to run twice with the comment
firejail --noprofile steam. this worked twice so far and i could have logged in with 2 different accounts.
The probelm is, if i start a the game on one, i can't get it run on another, i get the error

You can run only one instance at a time

This won't let me start the game a second time.
I think the sulution would be to Isolate the game procces or firejail itself. But the Question is, how?
Do you have any idea?

regards,
Alexey

Originally created by @Alexey2532 on GitHub (Apr 21, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1240 Hey, i was trying to run 2 games via 2 different firejails. i got Steam to run twice with the comment ` firejail --noprofile steam`. this worked twice so far and i could have logged in with 2 different accounts. The probelm is, if i start a the game on one, i can't get it run on another, i get the error > You can run only one instance at a time This won't let me start the game a second time. I think the sulution would be to Isolate the game procces or firejail itself. But the Question is, how? Do you have any idea? regards, Alexey

gitea-mirror

2026-05-05 06:58:01 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 06:58:06 -06:00

Author

Owner

@reinerh commented on GitHub (Apr 22, 2017):

You need to find out how they detect already running instances.
So perhaps you need to block certain protocols like netlink or unix sockets, or use private directories or blacklist certain directories/files. :)
Also you mentioned to run with --noprofile, which doesn't really isolate your processes.

@reinerh commented on GitHub (Apr 22, 2017): You need to find out how they detect already running instances. So perhaps you need to block certain protocols like netlink or unix sockets, or use private directories or blacklist certain directories/files. :) Also you mentioned to run with --noprofile, which doesn't really isolate your processes.

gitea-mirror commented

2026-05-05 06:58:09 -06:00

Author

Owner

@daniel11609 commented on GitHub (Apr 24, 2017):

How can I tell firejail to open a new sandbox... If I run the command firejail steam again it's not opening new instance.

@daniel11609 commented on GitHub (Apr 24, 2017): How can I tell firejail to open a new sandbox... If I run the command firejail steam again it's not opening new instance.

gitea-mirror commented

2026-05-05 06:58:10 -06:00

Author

Owner

@daniel11609 commented on GitHub (Apr 24, 2017):

OK probably just run it in new terminal but I have almost same problem, game already running

@daniel11609 commented on GitHub (Apr 24, 2017): OK probably just run it in new terminal but I have almost same problem, game already running

gitea-mirror commented

2026-05-05 06:58:12 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 26, 2017):

I think is the game doing it. As soon as you start the second instance, it detects another instance of the game running and is shutting down.

@netblue30 commented on GitHub (Apr 26, 2017): I think is the game doing it. As soon as you start the second instance, it detects another instance of the game running and is shutting down.

gitea-mirror commented

2026-05-05 06:58:15 -06:00

Author

Owner

@daniel11609 commented on GitHub (Apr 26, 2017):

Hey netblue...
Could you tell me how I can start even steam multiple times? Because using firejail steam doesn't seem to work. Only once...

Am 26. April 2017 13:56:03 MESZ schrieb netblue30 notifications@github.com:

I think is the game doing it. As soon as you start the second instance,
it detects another instance of the game running and is shutting down.

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/netblue30/firejail/issues/1240#issuecomment-297378757

@daniel11609 commented on GitHub (Apr 26, 2017): Hey netblue... Could you tell me how I can start even steam multiple times? Because using firejail steam doesn't seem to work. Only once... Am 26. April 2017 13:56:03 MESZ schrieb netblue30 <notifications@github.com>: >I think is the game doing it. As soon as you start the second instance, >it detects another instance of the game running and is shutting down. > >-- >You are receiving this because you commented. >Reply to this email directly or view it on GitHub: >https://github.com/netblue30/firejail/issues/1240#issuecomment-297378757

gitea-mirror commented

2026-05-05 06:58:17 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 26, 2017):

Try this: open /etc/firejail/steam.profile in a text editor and comment out all the lines in that file (add a # in front of each line), then try to start two instances of steam. If it works, it means one of the lines there is creating the problem - my guess would be private-tmp.

@netblue30 commented on GitHub (Apr 26, 2017): Try this: open /etc/firejail/steam.profile in a text editor and comment out all the lines in that file (add a # in front of each line), then try to start two instances of steam. If it works, it means one of the lines there is creating the problem - my guess would be private-tmp.

gitea-mirror commented

2026-05-05 06:58:20 -06:00

Author

Owner

@daniel11609 commented on GitHub (Apr 26, 2017):

Steam profile (applies to games/apps launched from Steam as well)

#noblacklist ${HOME}/.steam
#noblacklist ${HOME}/.local/share/steam
#include /etc/firejail/disable-mgmt.inc
#include /etc/firejail/disable-secret.inc
#include /etc/firejail/disable-common.inc
#include /etc/firejail/disable-devel.inc
#caps.drop all
#netfilter
#noroot
#seccomp
#protocol unix,inet,inet6

i open up a need terminal and do firejail steam. First time everythings fine, second time im getting this:
$ firejail steam
Reading profile /etc/firejail/steam.profile
Parent pid 5606, child pid 5607

Child process initialized
rm: cannot remove ‘/home/daniel/.steam/steam’: Is a directory
Running Steam on ubuntu 14.04 64-bit
STEAM_RUNTIME is enabled automatically

parent is shutting down, bye...
$

@daniel11609 commented on GitHub (Apr 26, 2017): # Steam profile (applies to games/apps launched from Steam as well) #noblacklist ${HOME}/.steam #noblacklist ${HOME}/.local/share/steam #include /etc/firejail/disable-mgmt.inc #include /etc/firejail/disable-secret.inc #include /etc/firejail/disable-common.inc #include /etc/firejail/disable-devel.inc #caps.drop all #netfilter #noroot #seccomp #protocol unix,inet,inet6 i open up a need terminal and do firejail steam. First time everythings fine, second time im getting this: $ firejail steam Reading profile /etc/firejail/steam.profile Parent pid 5606, child pid 5607 Child process initialized rm: cannot remove ‘/home/daniel/.steam/steam’: Is a directory Running Steam on ubuntu 14.04 64-bit STEAM_RUNTIME is enabled automatically parent is shutting down, bye... $

gitea-mirror commented

2026-05-05 06:58:22 -06:00

Author

Owner

@daniel11609 commented on GitHub (Apr 26, 2017):

and yea the game checks it after launch a message pops up:
Source - error:
only one instance can run at a time

@daniel11609 commented on GitHub (Apr 26, 2017): and yea the game checks it after launch a message pops up: Source - error: only one instance can run at a time

gitea-mirror commented

2026-05-05 06:58:23 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 26, 2017):

So I can close it, right?

@netblue30 commented on GitHub (Apr 26, 2017): So I can close it, right?

gitea-mirror commented

2026-05-05 06:58:25 -06:00

Author

Owner

@daniel11609 commented on GitHub (Apr 26, 2017):

But it doesn't work?

Am 26. April 2017 18:01:58 MESZ schrieb netblue30 notifications@github.com:

So I can close it, right?

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/netblue30/firejail/issues/1240#issuecomment-297459009

@daniel11609 commented on GitHub (Apr 26, 2017): But it doesn't work? Am 26. April 2017 18:01:58 MESZ schrieb netblue30 <notifications@github.com>: >So I can close it, right? > >-- >You are receiving this because you commented. >Reply to this email directly or view it on GitHub: >https://github.com/netblue30/firejail/issues/1240#issuecomment-297459009

gitea-mirror commented

2026-05-05 06:58:27 -06:00

Author

Owner

@daniel11609 commented on GitHub (Apr 26, 2017):

It doesn't work?

Am 26. April 2017 18:01:58 MESZ schrieb netblue30 notifications@github.com:

Closed #1240.

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/netblue30/firejail/issues/1240#event-1058906732

@daniel11609 commented on GitHub (Apr 26, 2017): It doesn't work? Am 26. April 2017 18:01:58 MESZ schrieb netblue30 <notifications@github.com>: >Closed #1240. > >-- >You are receiving this because you commented. >Reply to this email directly or view it on GitHub: >https://github.com/netblue30/firejail/issues/1240#event-1058906732

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#846

No description provided.

Rows
Columns