Skip to content
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 running Musescore on ChromeOS: bwrap: Can't mount proc on /newroot/proc: Operation not permitted #4631

Open
animeshadowpanda opened this issue Dec 23, 2021 · 5 comments
Labels
need more info sandbox issue related to sandbox setup

Comments

@animeshadowpanda
Copy link

animeshadowpanda commented Dec 23, 2021

Hey there, this the error I get:
flatpak run org.musescore.MuseScore
bwrap: Can't mount proc on /newroot/proc: Operation not permitted
error: ldconfig failed, exit status 256

I am on ChromeOS 96.0.4664.111, and Flatpak version 1.10.5.

@Ratevandr
Copy link

This bug report should be opened here: :https://github.com/flathub/org.musescore.MuseScore

@smcv
Copy link
Collaborator

smcv commented Jan 24, 2022

This bug report should be opened here: :https://github.com/flathub/org.musescore.MuseScore

Not necessarily: this looks more likely to be a general problem with running Flatpak apps on this particular machine (or on ChromeOS in general).

@animeshadowpanda, please try running a different Flatpak app like org.openttd.OpenTTD or org.kde.minuet to confirm whether this is a problem that is specific to Musescore, or a general problem with all Flatpak apps?

I am on ChromeOS 96.0.4664.111

I believe we've had issues in the past as a result of ChromeOS not being a typical Linux distribution.

We will need more information to have any chance of solving this. Please see https://github.com/flatpak/flatpak/blob/master/.github/ISSUE_TEMPLATE/bug_template.yml for the sort of information we need.

Other things that would be useful to know:

Are you running Flatpak in some sort of container, chroot, or other environment that is not the "real" operating system?

What is the output if you run flatpak run -vv org.musescore.MuseScore?

@smcv smcv changed the title Flatpak error when trying to run Musescore Error running Musescore on ChromeOS: bwrap: Can't mount proc on /newroot/proc: Operation not permitted Jan 24, 2022
@smcv smcv added need more info sandbox issue related to sandbox setup labels Jan 24, 2022
@smcv
Copy link
Collaborator

smcv commented Feb 11, 2022

Are you running Flatpak in some sort of container, chroot, or other environment that is not the "real" operating system?

The answer appears to be yes: the typical way to run Flatpak on ChromeOS is to run it under Crostini, which uses lxd containers.

If this is the same problem as in #3644, then this might help: https://www.reddit.com/r/Crostini/comments/rvjsi3/flatpak_apps_dont_work_in_chrome_os/hrbh6go/?utm_source=reddit&utm_medium=web2x&context=3

@Newbytee
Copy link

Newbytee commented May 10, 2024

This also happens reproduces when trying to build Flatpak packages with flatpak-builder in Bitbucket CI, maybe related to this: https://jira.atlassian.com/browse/BCLOUD-13420. Unfortunately the suggestion from Reddit isn't applicable in this case.

Is this worth opening a separate issue for?

@smcv
Copy link
Collaborator

smcv commented May 10, 2024

This also happens reproduces when trying to build Flatpak packages with flatpak-builder in Bitbucket CI, maybe related to this: https://jira.atlassian.com/browse/BCLOUD-13420.

If CAP_SYS_ADMIN is not available, then bubblewrap and therefore Flatpak cannot work. There is nothing that bubblewrap or flatpak can do to solve this: some container environments just cannot run them.

Is this worth opening a separate issue for?

Strictly speaking it's a separate issue, but we'd have to close it immediately as "won't fix" (or more accurately "can't fix"), so there isn't much point in opening it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need more info sandbox issue related to sandbox setup
Projects
None yet
Development

No branches or pull requests

4 participants