github-starred/firejail

Fork 0

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

[GH-ISSUE #3175] udiskie fails to open drive with seccomp blocking request_key #1990

New issue

Closed

opened 2026-05-05 08:39:21 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 08:39:21 -06:00

Owner

Originally created by @carloabelli on GitHub (Jan 22, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3175

udiskie fails to automatically open my drive when running under firejail.

When running udiskie without firejail, I get the notification that the drive has been added, then a popup to enter the drive password (the drive is LUKS encrypted).

When running under firejail, the notification that the drive has been added appears, but no prompt for my password appears. Unfortunately udiskie -v doesn't show any errors.

Adding ignore seccomp to udiskie.local fixes the issue.

Debugging the blocked syscalls it appears that request_key is being blocked and causing the hang.

Originally created by @carloabelli on GitHub (Jan 22, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3175 udiskie fails to automatically open my drive when running under firejail. When running udiskie without firejail, I get the notification that the drive has been added, then a popup to enter the drive password (the drive is LUKS encrypted). When running under firejail, the notification that the drive has been added appears, but no prompt for my password appears. Unfortunately `udiskie -v` doesn't show any errors. Adding `ignore seccomp` to `udiskie.local` fixes the issue. Debugging the blocked syscalls it appears that `request_key` is being blocked and causing the hang.

gitea-mirror closed this issue

2026-05-05 08:39:22 -06:00

gitea-mirror commented

2026-05-05 08:39:24 -06:00

Author

Owner

@carloabelli commented on GitHub (Jan 22, 2020):

Can confirm that adding seccomp !request_key resolves the issue.

@carloabelli commented on GitHub (Jan 22, 2020): Can confirm that adding `seccomp !request_key` resolves the issue.

gitea-mirror commented

2026-05-05 08:39:25 -06:00

Author

Owner

@rusty-snake commented on GitHub (Jan 22, 2020):

@carloabelli open a PR

@rusty-snake commented on GitHub (Jan 22, 2020): @carloabelli open a PR

gitea-mirror commented

2026-05-05 08:39:26 -06:00

Author

Owner

@carloabelli commented on GitHub (Jan 22, 2020):

@rusty-snake Done. Wasn't sure if the workaround was sufficient here like it was in #2681. I have also opened a PR for that issue in case it is now best practice to fix the default profiles.

@carloabelli commented on GitHub (Jan 22, 2020): @rusty-snake Done. Wasn't sure if the workaround was sufficient here like it was in #2681. I have also opened a PR for that issue in case it is now best practice to fix the default profiles.

gitea-mirror referenced this issue

2026-05-05 08:49:11 -06:00

[GH-ISSUE #3413] u2f key is not detected in the browser #2143

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

No description provided.

Rows
Columns