-
Notifications
You must be signed in to change notification settings - Fork 567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: failed to run /run/firejail/lib/fcopy #3741
Comments
Seems to be related to a combination of private-bin and private-etc. |
Commenting out private-lib in transmission-common.profile also helps. |
Yea I observed the same on Sid. I suggest to comment out |
That would workaround it for transmission only. But the same issue happens for other profiles as well. |
I've |
|
Ah, ok I wasn't aware of that.
…On November 12, 2020 8:54:06 AM UTC, Reiner Herrmann ***@***.***> wrote:
That would workaround it for transmission only. But the same issue
happens for other profiles as well.
|
@smitsohu This issue seems to be back.
Could it be related to the change in 1e3891e? |
Mmmh, in the moment I have problems reproducing the issue on Bullseye.
Instead I went with your other idea
firejail/src/firejail/fs_lib2.c Line 42 in af23753
|
Here is a debug log:
While it is |
|
@reinerh If you find the time, could you try if adding back Maybe we could run fldd as root on our helper binaries? After all we have to trust them anyway. |
@smitsohu I tried it, but it didn't help:
|
And if you relax permissions on |
@smitsohu With |
Just trying to understand what is going on: Is it possible you have libpcre2 in a place unexpected to firejail? (what does |
|
Quite interesting. I have really no idea atm why I'll try to put together a pull request to run this stuff as root. Then we have read permission on fcopy and it should work again. |
@reinerh Do we have any time pressure here (= do you need this for one of your builds)? Just asking. |
@smitsohu I don't think there is much pressure. If you can't reproduce it, it's maybe not so widespread and only occurs on certain systems. It would be nice if it could be fixed by 1st of March, as I could then still apply a patch to the version packaged in Debian, and it would make it into the next stable (though fixing it later is probably also still possible if the change is not intrusive and we can argue it's important enough to fix). If you want me to test or debug anything, please tell me. |
Ok. I'll try to have something by the weekend. |
A user reported issues with starting transmission-cli with firejail, and I'm able to reproduce it.
I also see the same error a couple of times with different profiles when running the test-profiles part of the test suite.
The text was updated successfully, but these errors were encountered: