[GH-ISSUE #2368] ark, private-tmp and browsers #1576

Closed
opened 2026-05-05 08:14:05 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @ghost on GitHub (Jan 24, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2368

the Ark profile is using private- tmp, this option breaks "open file" in browsers
2019-01-24_18-38

it seems not possible to use private-tmp folder* nor private-tmp and noblacklist /tmp/folder*

should this option be removed from the default profile?

2019-01-24_18-46
2019-01-24_18-46_1

Originally created by @ghost on GitHub (Jan 24, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2368 the Ark profile is using `private- tmp`, this option breaks "open file" in browsers ![2019-01-24_18-38](https://user-images.githubusercontent.com/45907176/51700512-a7017680-200f-11e9-94e1-1da7a74bcd20.png) it seems not possible to use `private-tmp folder*` nor `private-tmp` and `noblacklist /tmp/folder*` should this option be removed from the default profile? ![2019-01-24_18-46](https://user-images.githubusercontent.com/45907176/51701043-d9f83a00-2010-11e9-8866-6871a4bf07ad.png) ![2019-01-24_18-46_1](https://user-images.githubusercontent.com/45907176/51701050-dbc1fd80-2010-11e9-9034-739c65a84b7d.png)
gitea-mirror 2026-05-05 08:14:05 -06:00
Author
Owner

@Vincent43 commented on GitHub (Jan 24, 2019):

You may use ignore private-tmp.

<!-- gh-comment-id:457311797 --> @Vincent43 commented on GitHub (Jan 24, 2019): You may use `ignore private-tmp`.
Author
Owner

@Fred-Barclay commented on GitHub (Jan 25, 2019):

Agree with @Vincent43 . It's a tad annoying, but private-tmp is worth the benefits.

<!-- gh-comment-id:457446928 --> @Fred-Barclay commented on GitHub (Jan 25, 2019): Agree with @Vincent43 . It's a tad annoying, but `private-tmp` is worth the benefits.
Author
Owner

@chiraag-nataraj commented on GitHub (Feb 7, 2019):

I'm going to go ahead and close this issue, since this is (effectively) intended behavior and a fix was proposed in the OP's case.

<!-- gh-comment-id:461509787 --> @chiraag-nataraj commented on GitHub (Feb 7, 2019): I'm going to go ahead and close this issue, since this is (effectively) intended behavior and a fix was proposed in the OP's case.
Sign in to join this conversation.
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#1576
No description provided.