mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3216] Problem running Cura-4.4.1.appimage with Firejail #2015
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2015
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FlailAway on GitHub (Feb 9, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3216
Hi All, I am trying to run Cura 4.4.1.appimage within firejail, but it balks with errors.
I need to contain Cura as it bullies all/any other open Serial ports and closes them all. My Arduino IoT stuff keeps dropping Serial connections and it is just plain irritating. I have disabled all of the Cura-Marketplace add-ons (as suggested by Cura Devs) items likely to mess with the Serial ports but still it happens about one minute after starting Cura or saving an .obj or .gcode file.
firejail --appimage --private /home/tester/desktop/Cura-4.4.1.appimage
OR
firejail --appimage --private --seccomp /home/tester/desktop/Cura-4.4.1.appimage
Gives me
"Dropping all Linux capabilities and enforcing default seccomp filter"
"Segmentation fault (core dumped)"
"Parent is shutting down, bye..."
This stops Cura.
Can someone please help me with this.
Thanks
@rusty-snake commented on GitHub (Feb 10, 2020):
First off put --appimage as last firejail argument: firejail --private --appimage /home/tester/desktop/Cura-4.4.1.appimage. Works it with --noprofile to start it? Is anything in the journal that gives a hint? What is you firejail version?
@FlailAway commented on GitHub (Feb 10, 2020):
I am using Mint 19.3, all up to date. Thanks you for your quick reply, very much appreciated. Firjail is Version 0.9.52. Moving --appimage to the last place for an option gave the same result as above.
Where will I find the "journal?" I looked in "etc/firejail" but nothing there looks like a Log.
Using --noprofile shows 3-errors and locks up with the Cura Splash screen showing.
"Fontconfig error: "/etc/fonts/co"nf.d/10-scale-bitmap-fonts.conf Line 72: non-double matrix element
"Fontconfig error: "/etc/fonts/co"nf.d/10-scale-bitmap-fonts.conf Line 72: non-double matrix element
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 80: saw unknown expected number
Cura can be downloaded from here if you need it.
https://github.com/Ultimaker/Cura/releases
@rusty-snake commented on GitHub (Feb 10, 2020):
journalctl --pager-end@rusty-snake commented on GitHub (Feb 10, 2020):
Has you tested --noprofile without future arguments (except --appimage)?
@FlailAway commented on GitHub (Feb 10, 2020):
Thanks again.
Yes, both ways when testing as you suggested above. When I use --noprofile --appimage that is when I got the fonts errors and Cura-freeze I mentioned above.
There may be typos in those error lines as I have to copy them from the 3D-printing PC that is not online. But, pretty sure I have them correct.
@rusty-snake commented on GitHub (Feb 10, 2020):
I can start it with this command:
firejail --noprofile --private --net=none --nodbus --appimage Cura-4.4.1.AppImageFedora 31 + firejail git.
seccomprequires mbind.@FlailAway commented on GitHub (Feb 11, 2020):
Hi, thanks again. The 3D printer PC does not normally have Internet access so I downloaded the .deb version 0.9.62 from SourceForge as the Repo version I had (v0.9.52) did not understand --nodbus. The v0.9.62 ran OK, but it seems too restrictive as it start Cura from new every time and I have to configure the printer each time I use it.
I suspect I was expecting too much from FireJail as I had hoped I could configure it to allow everything (load files to print and save the .gcode files to SD/USB) as usual each time I run it, but it must prohibit all Cura access to the Serial ports.
I was thinking that once a Sandbox hade been built around Cura, I could just restart that same sandbox each time.
There is some errant code in Cura that is closing all the Serial ports after about a minute of starting or some time after I save a file. The Cura-devs fixed it a few versions back but it has returned in 4.4.1 and so far the devs seem to have no interest in fixing it.
Unless I can stop Cura from all access to the Serial ports, I guess I will just have to put it with restarting put IoT stuff many times a day. Or, move Cura to it's own PC. I might try running Cura in a VM and see if that stops it messing with the Serial ports.
Thank you very much for your efforts to get this working for me.
@rusty-snake commented on GitHub (Feb 11, 2020):
You need to drop
--privateso that cura can save it's settings. With --private is $HOME a tmpfs.@FlailAway commented on GitHub (Feb 11, 2020):
Awesome, thank you, that seems to have solved it. I can use the existing setup for Cura and so far it has not shut down any Serial ports.