[GH-ISSUE #2768] join-or-start on multi-user systems #1738

New issue

Open

opened 2026-05-05 08:24:37 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

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

Owner

Originally created by @SkewedZeppelin on GitHub (Jun 13, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2768

join-or-start breaks programs when currently running under another user.

Example:

User A logs in, opens a document in LibreOffice
User B either switches user or connects to shared box like X2Go
User B tries to open a document in LibreOffice
- LibreOffice never opens as firejail prevents joining a sandbox by another user

I know firejail has been primarily designed for single-user systems, but join-or-start should simply only attempt to join a sandbox owned by the current user and never attempt to join that of another user.

Originally created by @SkewedZeppelin on GitHub (Jun 13, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2768 join-or-start breaks programs when currently running under another user. Example: - User A logs in, opens a document in LibreOffice - User B either switches user or connects to shared box like X2Go - User B tries to open a document in LibreOffice - LibreOffice never opens as firejail prevents joining a sandbox by another user I know firejail has been primarily designed for single-user systems, but join-or-start should simply only attempt to join a sandbox owned by the current user and never attempt to join that of another user.

gitea-mirror added the

bug

label 2026-05-05 08:24:37 -06:00

gitea-mirror commented

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

Author

Owner

@b-misc commented on GitHub (Nov 5, 2019):

I can confirm that behaviour and due to #1391 I find myself now forced to switch between two bad options on this multi-user system:

either I use join-or-start breaking several users working the same time on the same machine using the same applications
or I use ignore join-or-start breaking ability to start another instance of an application for the same user (see #1391)

@b-misc commented on GitHub (Nov 5, 2019): I can confirm that behaviour and due to #1391 I find myself now forced to switch between two bad options on this multi-user system: - either I use join-or-start breaking several users working the same time on the same machine using the same applications - or I use ignore join-or-start breaking ability to start another instance of an application for the same user (see #1391)

gitea-mirror referenced this issue

2026-05-05 10:12:55 -06:00

[PR #1738] [MERGED] add new syscalls from glibc 2.26-10 #4056

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

No description provided.

Rows
Columns