github-starred/firejail

Fork 0

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

[GH-ISSUE #845] LibreOffice doesn't start #574

New issue

Closed

opened 2026-05-05 06:12:16 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 06:12:16 -06:00

Owner

Originally created by @curiosity-seeker on GitHub (Oct 8, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/845

After the latest change for libreoffice.profile, LibreOffice (v. 5.1.5.2 on Fedora 24) doesn't start anymore. On the console I'm getting the error

Failed to open display

The problem is fixed after uncommenting

# whitelist /tmp/.X11-unix/

Originally created by @curiosity-seeker on GitHub (Oct 8, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/845 After the latest change for libreoffice.profile, LibreOffice (v. 5.1.5.2 on Fedora 24) doesn't start anymore. On the console I'm getting the error `Failed to open display` The problem is fixed after _uncommenting_ `# whitelist /tmp/.X11-unix/`

gitea-mirror

2026-05-05 06:12:16 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 06:12:23 -06:00

Author

Owner

@netblue30 commented on GitHub (Oct 9, 2016):

I'll look into it, thanks.

@netblue30 commented on GitHub (Oct 9, 2016): I'll look into it, thanks.

gitea-mirror commented

2026-05-05 06:12:25 -06:00

Author

Owner

@valoq commented on GitHub (Oct 9, 2016):

Whitelisting /temp/.X11-unix only restricts the profile further. Therefore it shouldn't help. Am I missing something?

Also whitelisting this directory will prevent libreoffice from writing several temporary files, necessary for recovering documents after a crash.

Are you by any chance using additional firejail options?
I have seen that issue when using "net none" in a profile.

@valoq commented on GitHub (Oct 9, 2016): Whitelisting /temp/.X11-unix only restricts the profile further. Therefore it shouldn't help. Am I missing something? Also whitelisting this directory will prevent libreoffice from writing several temporary files, necessary for recovering documents after a crash. Are you by any chance using additional firejail options? I have seen that issue when using "net none" in a profile.

gitea-mirror commented

2026-05-05 06:12:28 -06:00

Author

Owner

@valoq commented on GitHub (Oct 9, 2016):

I tried to recreate the issue on a fresh fedora 24 system but libreoffice starts just fine.
Can you please provide more information about how you start libreoffice?

@valoq commented on GitHub (Oct 9, 2016): I tried to recreate the issue on a fresh fedora 24 system but libreoffice starts just fine. Can you please provide more information about how you start libreoffice?

gitea-mirror commented

2026-05-05 06:12:29 -06:00

Author

Owner

@curiosity-seeker commented on GitHub (Oct 9, 2016):

Well, I created the necessary symlinks for Firejail as usual with sudo firecfg and start LibreOffice via the KDE start menu.

That error message mentioned in the first post was shown when I started it on the console.

@curiosity-seeker commented on GitHub (Oct 9, 2016): Well, I created the necessary symlinks for Firejail as usual with sudo firecfg and start LibreOffice via the KDE start menu. That error message mentioned in the first post was shown when I started it on the console.

gitea-mirror commented

2026-05-05 06:12:31 -06:00

Author

Owner

@valoq commented on GitHub (Oct 9, 2016):

Using the default fedora 24 system with gnome, Libreoffice 5.1.5.2 and firejail 0.9.43 from today, I was not able to recreate the issue.
Maybe netblue has an Idea why whitelisting could solve anything in the first place.

@valoq commented on GitHub (Oct 9, 2016): Using the default fedora 24 system with gnome, Libreoffice 5.1.5.2 and firejail 0.9.43 from today, I was not able to recreate the issue. Maybe netblue has an Idea why whitelisting could solve anything in the first place.

gitea-mirror commented

2026-05-05 06:12:32 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Oct 9, 2016):

Can you post the full profile (or attach it)? I have a sneaking suspicion that there's a private-tmp there which, along with a net none, would completely disable access to X11. Hence you would need to whitelist the X11 unix socket.

@chiraag-nataraj commented on GitHub (Oct 9, 2016): Can you post the full profile (or attach it)? I have a sneaking suspicion that there's a `private-tmp` there which, along with a `net none`, would completely disable access to `X11`. Hence you would need to whitelist the `X11` unix socket.

gitea-mirror commented

2026-05-05 06:12:34 -06:00

Author

Owner

@curiosity-seeker commented on GitHub (Oct 10, 2016):

Okay, I found the culprit. I had added the following rule

whitelist /tmp/mozilla_hank0/

to my individual profile as without this rule LibreOffice wouldn't open attachments in Thunderbird mails. Now I've commented that rule and everything works as it should - even opening those attachments.

I don't fully understand the nexus but all is well - sorry for the trouble!

@curiosity-seeker commented on GitHub (Oct 10, 2016): Okay, I found the culprit. I had added the following rule `whitelist /tmp/mozilla_hank0/` to my individual profile as without this rule LibreOffice wouldn't open attachments in Thunderbird mails. Now I've commented that rule and everything works as it should - even opening those attachments. I don't fully understand the nexus but all is well - sorry for the trouble!

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

No description provided.

Rows
Columns