github-starred/firejail

Fork 0

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

[GH-ISSUE #1422] mutt + gpg indefinitely hangs #969

New issue

Closed

opened 2026-05-05 07:14:08 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:14:08 -06:00

Owner

Originally created by @chiraag-nataraj on GitHub (Jul 31, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1422

Because of pid namespaces, gpg is unable to find the running instance of gpg-agent, so it creates a new one. Then, since that process is running in the sandbox, the sandbox never closes. I initially thought this was a bug with my profile, but it turns out I have this problem with the default profile as well.

Originally created by @chiraag-nataraj on GitHub (Jul 31, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1422 Because of pid namespaces, `gpg` is unable to find the running instance of `gpg-agent`, so it creates a new one. Then, since that process is running in the sandbox, the sandbox never closes. I initially thought this was a bug with my profile, but it turns out I have this problem with the default profile as well.

gitea-mirror closed this issue

2026-05-05 07:14:10 -06:00

gitea-mirror commented

2026-05-05 07:14:12 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 31, 2017):

Okay, this happened after firejail 0.9.48, because the version I've installed from the repository still works, but the development version I forked to get xpra working again ends up breaking this. It's not the xpra stuff because not launching mutt in the X11 sandbox still produces the same effect/issue.

@chiraag-nataraj commented on GitHub (Jul 31, 2017): Okay, this happened after firejail 0.9.48, because the version I've installed from the repository still works, but the development version I forked to get `xpra` working again ends up breaking this. It's not the `xpra` stuff because not launching `mutt` in the X11 sandbox still produces the same effect/issue.

gitea-mirror commented

2026-05-05 07:14:14 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 31, 2017):

Okay, this is an instance of #725.

@chiraag-nataraj commented on GitHub (Jul 31, 2017): Okay, this is an instance of #725.

gitea-mirror commented

2026-05-05 07:14:16 -06:00

Author

Owner

@SkewedZeppelin commented on GitHub (Jul 31, 2017):

I wonder if we can add "join-or-start gpg" to both gpg.profile and gpg-agent.profile so that they can see each other. I just don't know what effects that'll have cross-user.

And for a fix for #725 I wonder if Firejail should internally perform "join-or-start program" all the time except for profiles with "private" in order to prevent issues for example clicking a link in a non firejailed program while a firejailed browser is already open.

@SkewedZeppelin commented on GitHub (Jul 31, 2017): I wonder if we can add "join-or-start gpg" to both gpg.profile and gpg-agent.profile so that they can see each other. I just don't know what effects that'll have cross-user. And for a fix for #725 I wonder if Firejail should internally perform "join-or-start program" all the time except for profiles with "private" in order to prevent issues for example clicking a link in a non firejailed program while a firejailed browser is already open.

gitea-mirror commented

2026-05-05 07:14:18 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Aug 1, 2017):

I don't know if that would solve this case, though, where I start another program which then happens to call gpg (rather than me launching it separately).

@chiraag-nataraj commented on GitHub (Aug 1, 2017): I don't know if that would solve this case, though, where I start another program which then happens to call `gpg` (rather than me launching it separately).

gitea-mirror commented

2026-05-05 07:14:19 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Mar 29, 2018):

Fixed by using writable-run-user to allow access to the systemd-instantiated gpg-agent socket.

@chiraag-nataraj commented on GitHub (Mar 29, 2018): Fixed by using `writable-run-user` to allow access to the systemd-instantiated gpg-agent socket.

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

No description provided.

Rows
Columns