#373 - [GH-ISSUE #531] polly - not running under firejail control ? - github-starred/firejail

gitea-mirror commented

2026-05-05 05:43:11 -06:00

Owner

Originally created by @frank-github on GitHub (May 21, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/531

try to run polly under firejail control
application run and works, but seems not to be controlled by firejail, isn't ?

ubuntu:~/.config/firejail$ firejail --private=/media/daten/frank/Firejail/Polly polly
Reading profile /media/daten/frank/.config/firejail/polly.profile
Reading profile /etc/firejail/disable-mgmt.inc
Reading profile /etc/firejail/disable-secret.inc
Reading profile /etc/firejail/disable-common.inc
Parent pid 15068, child pid 15069

Warning: --protocol not supported on this platform
Child process initialized

parent is shutting down, bye...
ubuntu:~/.config/firejail$ firejail --list
ubuntu:~/.config/firejail$

Originally created by @frank-github on GitHub (May 21, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/531 try to run polly under firejail control application run and works, but seems not to be controlled by firejail, isn't ? ``` ubuntu:~/.config/firejail$ firejail --private=/media/daten/frank/Firejail/Polly polly Reading profile /media/daten/frank/.config/firejail/polly.profile Reading profile /etc/firejail/disable-mgmt.inc Reading profile /etc/firejail/disable-secret.inc Reading profile /etc/firejail/disable-common.inc Parent pid 15068, child pid 15069 Warning: --protocol not supported on this platform Child process initialized parent is shutting down, bye... ubuntu:~/.config/firejail$ firejail --list ubuntu:~/.config/firejail$ ```

gitea-mirror

2026-05-05 05:43:11 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 05:43:17 -06:00

Author

Owner

@netblue30 commented on GitHub (May 23, 2016):

Probably Polly is a single-instance program. When you start it, it checks if another instance is already running. If one is found, it sends a message and it shuts down. The existing instance will then open the application windows.

Lots of programs do this, among them Firefox. Make sure the first instance of polly is started under firejail.

@netblue30 commented on GitHub (May 23, 2016): Probably Polly is a single-instance program. When you start it, it checks if another instance is already running. If one is found, it sends a message and it shuts down. The existing instance will then open the application windows. Lots of programs do this, among them Firefox. Make sure the first instance of polly is started under firejail.

gitea-mirror commented

2026-05-05 05:43:19 -06:00

Author

Owner

@frank-github commented on GitHub (May 23, 2016):

hupps, I never noticed polly didn't quit, if I close it by X button
thanks, if polly not running, everything works fine :-)

@frank-github commented on GitHub (May 23, 2016): hupps, I never noticed polly didn't quit, if I close it by X button thanks, if polly not running, everything works fine :-)

gitea-mirror commented

2026-05-05 05:43:21 -06:00

Author

Owner

@frank-github commented on GitHub (May 23, 2016):

need another polly related tip
application uses old original homepath, but firejail was run with --private=/newdir
maybe read user home directory from /etc/passwd ??

ubuntu:$ firejail --private=/media/daten/user/Firejail/Polly polly

cache path: /media/daten/user/.cache/polly
config path: /media/daten/user/.config/polly
data home: /media/daten/user/.local/share/polly
/usr/bin/polly:332: GtkWarning: Attempting to store changes into /media/daten/user/.local/share/recently-used.xbel', but failed: Datei »/media/daten/user/.local/share/recently-used.xbel.GARBIY« konnte nicht angelegt werden: Datei oder Verzeichnis nicht gefunden Gtk.main() /usr/bin/polly:332: GtkWarning: Attempting to set the permissions of/media/daten/user/.local/share/recently-used.xbel', but failed: Datei oder Verzeichnis nicht gefunden
Gtk.main()

any hint or tip is welcome

@frank-github commented on GitHub (May 23, 2016): need another polly related tip application uses old original homepath, but firejail was run with --private=/newdir maybe read user home directory from /etc/passwd ?? `ubuntu:$ firejail --private=/media/daten/user/Firejail/Polly polly` cache path: /media/daten/**user**/.cache/polly config path: /media/daten/**user**/.config/polly data home: /media/daten/**user**/.local/share/polly /usr/bin/polly:332: GtkWarning: Attempting to store changes into `/media/daten/user/.local/share/recently-used.xbel', but failed: Datei »/media/daten/user/.local/share/recently-used.xbel.GARBIY« konnte nicht angelegt werden: Datei oder Verzeichnis nicht gefunden Gtk.main() /usr/bin/polly:332: GtkWarning: Attempting to set the permissions of`/media/daten/user/.local/share/recently-used.xbel', but failed: Datei oder Verzeichnis nicht gefunden Gtk.main() any hint or tip is welcome

gitea-mirror commented

2026-05-05 05:43:24 -06:00

Author

Owner

@netblue30 commented on GitHub (May 25, 2016):

You need to create the directories in the new home:

$ mkdir /media/daten/user/Firejail/Polly/.cache
$ mkdir /media/daten/user/Firejail/Polly/.config
$ mkdir -p /media/daten/user/Firejail/Polly/.local/share

It is strange, most programs do this by default. If they don't find a ~/.config directory they just create it.

@netblue30 commented on GitHub (May 25, 2016): You need to create the directories in the new home: ``` $ mkdir /media/daten/user/Firejail/Polly/.cache $ mkdir /media/daten/user/Firejail/Polly/.config $ mkdir -p /media/daten/user/Firejail/Polly/.local/share ``` It is strange, most programs do this by default. If they don't find a ~/.config directory they just create it.

gitea-mirror commented

2026-05-05 05:43:25 -06:00

Author

Owner

@frank-github commented on GitHub (May 25, 2016):

I did create this folders in "new firejail" home, but polly still try to access old locations 👎

@frank-github commented on GitHub (May 25, 2016): I did create this folders in "new firejail" home, but polly still try to access old locations :-1:

gitea-mirror commented

2026-05-05 05:43:28 -06:00

Author

Owner

@netblue30 commented on GitHub (May 26, 2016):

It means polly is already running in the background somewhere.

@netblue30 commented on GitHub (May 26, 2016): It means polly is already running in the background somewhere.

gitea-mirror commented

2026-05-05 05:43:29 -06:00

Author

Owner

@frank-github commented on GitHub (May 26, 2016):

for sure, no polly instance running on this maschine, if I start it with firejail and got this output !

@frank-github commented on GitHub (May 26, 2016): for sure, no polly instance running on this maschine, if I start it with firejail and got this output !

gitea-mirror commented

2026-05-05 05:43:31 -06:00

Author

Owner

@netblue30 commented on GitHub (May 31, 2016):

I'll give it a try.

@netblue30 commented on GitHub (May 31, 2016): I'll give it a try.

gitea-mirror commented

2026-05-05 05:43:33 -06:00

Author

Owner

@netblue30 commented on GitHub (Jun 11, 2016):

Polly runs as a daemon. You start it for the first time and shut it down, and polly goes in the background instead of shutting down. You will no see anything on your screen, but polly is there waiting for commands.

When you start it the second time, the new polly instance sends a message to the one in the background, and the background instance opens the application window. Then, the second instance shuts down.

The fix is to make sure the first instance is started in firejail. I would add a symbolic link in /usr/local/bin:

$ sudo ln -s /usr/bin/firejail /usr/local/bin/polly

This way, polly is always sandboxed, including the first instance. You will need to reboot the computer after you add the link. After the computer starts up, use Dash (the top icon in the Launcher to find polly, and click on the polly icon - it should start polly in firejail. You can use "firejail --list" in a terminal to see if polly is sandboxed.

@netblue30 commented on GitHub (Jun 11, 2016): Polly runs as a daemon. You start it for the first time and shut it down, and polly goes in the background instead of shutting down. You will no see anything on your screen, but polly is there waiting for commands. When you start it the second time, the new polly instance sends a message to the one in the background, and the background instance opens the application window. Then, the second instance shuts down. The fix is to make sure the first instance is started in firejail. I would add a symbolic link in /usr/local/bin: ``` $ sudo ln -s /usr/bin/firejail /usr/local/bin/polly ``` This way, polly is always sandboxed, including the first instance. You will need to reboot the computer after you add the link. After the computer starts up, use Dash (the top icon in the Launcher to find polly, and click on the polly icon - it should start polly in firejail. You can use "firejail --list" in a terminal to see if polly is sandboxed.

Rows
Columns

[GH-ISSUE #531] polly - not running under firejail control ? #373