github-starred/firejail

Fork 0

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

[GH-ISSUE #5726] signal-desktop: program fails on startup #3077

New issue

Closed

opened 2026-05-05 09:43:09 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 09:43:09 -06:00

Owner

Originally created by @kmk3 on GitHub (Mar 9, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5726

Discussed in https://github.com/netblue30/firejail/discussions/5725

^{Originally posted by rieje March 9, 2023}
Anyone have a guess why signal-desktop fails on system startup? I run it as a systemd user service. It pretty much never starts on startup and I need to restart the service and then it will launch. On the rare occasion I think it might randomly crash but I'm not sure. If I don't run it without firejail it works fine without fail. Here's systemd service status. I'm on Wayland (Sway).

Originally created by @kmk3 on GitHub (Mar 9, 2023). Original GitHub issue: https://github.com/netblue30/firejail/issues/5726 ### Discussed in https://github.com/netblue30/firejail/discussions/5725 <div type='discussions-op-text'> <sup>Originally posted by **rieje** March 9, 2023</sup> Anyone have a guess why signal-desktop fails on system startup? I run it as a systemd user service. It pretty much never starts on startup and I need to restart the service and then it will launch. On the rare occasion I think it might randomly crash but I'm not sure. If I don't run it without firejail it works fine without fail. Here's [systemd service status](https://0x0.st/HiAg.txt). I'm on Wayland (Sway).</div>

gitea-mirror closed this issue

2026-05-05 09:43:10 -06:00

gitea-mirror commented

2026-05-05 09:43:11 -06:00

Author

Owner

@kmk3 commented on GitHub (Mar 9, 2023):

Basic debugging information is missing; please follow the bug report template
(in a new comment or in a new issue):

https://github.com/netblue30/firejail/issues/new?template=bug_report.md

@kmk3 commented on GitHub (Mar 9, 2023): Basic debugging information is missing; please follow the bug report template (in a new comment or in a new issue): * <https://github.com/netblue30/firejail/issues/new?template=bug_report.md>

gitea-mirror commented

2026-05-05 09:43:13 -06:00

Author

Owner

@rieje commented on GitHub (Mar 9, 2023):

I would think firejail[1165]: Access error: uid 1000, last mount name:/ dir:/run/user/1000/gvfs type:fuse.gvfsd-fuse - invalid noexec mount would be relevant. It doesn't seem straightforward to debug it since it only happens once on system startup but I'll give it another go if I have the time.

@rieje commented on GitHub (Mar 9, 2023): I would think `firejail[1165]: Access error: uid 1000, last mount name:/ dir:/run/user/1000/gvfs type:fuse.gvfsd-fuse - invalid noexec mount` would be relevant. It doesn't seem straightforward to debug it since it only happens once on system startup but I'll give it another go if I have the time.

gitea-mirror commented

2026-05-05 09:43:14 -06:00

Author

Owner

@kmk3 commented on GitHub (Mar 23, 2023):

@rieje

Sorry for the delay.

please follow the bug report template

I realize now that since I opened this myself, you probably can't update
anything in the first comment.

GitHub's UX for converting a discussion into an issue is lacking.

Could you open a new issue yourself?

Here's systemd service status. I'm on Wayland
(Sway).

Also, unless you want to avoid GitHub specifically, could you upload this file
in the new issue itself?

It should be possible to just drag and drop it in a comment.

@kmk3 commented on GitHub (Mar 23, 2023): @rieje Sorry for the delay. > please follow the bug report template I realize now that since I opened this myself, you probably can't update anything in the first comment. GitHub's UX for converting a discussion into an issue is lacking. Could you open a new issue yourself? > Here's [systemd service status](https://0x0.st/HiAg.txt). I'm on Wayland > (Sway). Also, unless you want to avoid GitHub specifically, could you upload this file in the new issue itself? It should be possible to just drag and drop it in a comment.

gitea-mirror referenced this issue

2026-05-05 10:23:44 -06:00

[PR #3077] [MERGED] gpg additions #4633

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

No description provided.

Rows
Columns