github-starred/firejail

Fork 0

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

[GH-ISSUE #298] [spotify] When never run without being firejailed, “remember me” doesn't work (directories under $HOME on whitelist cannot be created when not existent) #208

New issue

Closed

opened 2026-05-05 05:19:41 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:19:41 -06:00

Owner

Originally created by @blipp on GitHub (Feb 15, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/298

The Spotify profile includes the following whitelist entries:

whitelist ${HOME}/.config/spotify
whitelist ${HOME}/.local/share/spotify
whitelist ${HOME}/.cache/spotify

The first for example is needed to save user credentials when using the “remember me” function. However, if Spotify was never started without being firejailed, those directories don't exist and wont/can't be created. As a result, Spotify can't remember my user (and probably other stuff under the hood because of the other two directories).

Workaround: I created those directories manually. Now “remember me” works.

Any ideas how to solve this in general? (I would like to avoid “run it once without Firejail”, because of security reasons)

Originally created by @blipp on GitHub (Feb 15, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/298 The Spotify profile includes the following whitelist entries: ``` whitelist ${HOME}/.config/spotify whitelist ${HOME}/.local/share/spotify whitelist ${HOME}/.cache/spotify ``` The first for example is needed to save user credentials when using the “remember me” function. However, if Spotify was never started without being firejailed, those directories don't exist and wont/can't be created. As a result, Spotify can't remember my user (and probably other stuff under the hood because of the other two directories). Workaround: I created those directories manually. Now “remember me” works. Any ideas how to solve this in general? (I would like to avoid “run it once without Firejail”, because of security reasons)

gitea-mirror

2026-05-05 05:19:41 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:19:48 -06:00

Author

Owner

@blipp commented on GitHub (Feb 15, 2016):

Maybe something like, just as a quick idea, without knowing the internals good enough: if a directory is whitelisted, the process should be allowed to create it persistently?

@blipp commented on GitHub (Feb 15, 2016): Maybe something like, just as a quick idea, without knowing the internals good enough: if a directory is whitelisted, the process should be allowed to create it persistently?

gitea-mirror commented

2026-05-05 05:19:51 -06:00

Author

Owner

@netblue30 commented on GitHub (Feb 16, 2016):

I'll bring in a new command (mkdir) in profile files that will create the necessary directories.

@netblue30 commented on GitHub (Feb 16, 2016): I'll bring in a new command (mkdir) in profile files that will create the necessary directories.

gitea-mirror commented

2026-05-05 05:19:54 -06:00

Author

Owner

@blipp commented on GitHub (Feb 16, 2016):

Thanks!

@blipp commented on GitHub (Feb 16, 2016): Thanks!

gitea-mirror commented

2026-05-05 05:19:56 -06:00

Author

Owner

@netblue30 commented on GitHub (Feb 20, 2016):

Fixed! I've also included mkdir in all whitelisting profiles.

@netblue30 commented on GitHub (Feb 20, 2016): Fixed! I've also included mkdir in all whitelisting profiles.

gitea-mirror referenced this issue

2026-05-05 09:07:45 -06:00

[GH-ISSUE #3892] Option to launch firejailed program as a different user #2444

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#208

No description provided.

Rows
Columns