🐞 Bug - Flatpak not working
Describe the bug Can't launch flatpak apps
To Reproduce Steps to reproduce the behavior:
- Please indicate where the command(s) were executed.
a. Install flatpak
crew install flatpak
b. Install flatpak app
flatpak install flathub org.gimp.GIMP
c. Run this app
flatpak run org.gimp.GIMP
My environment was (crosh, bash or VT-2):
-
I executed the command(s) below:
flatpak run org.gimp.GIMPOutput:
ln: failed to create symbolic link '/home/chronos/user/.local/share/fonts': File exists env: 'ruby': No such file or directory env: 'ruby': No such file or directory bwrap: Failed to make / slave: Operation not permitted env: 'ruby': No such file or directory error: ldconfig failed, exit status 32512
Expected behavior Open flatpak app
Screenshots
System Information: Paste the output of crew sysinfo -v between the two *** below.
If you cannot execute crew, display the output of cat /etc/lsb-release instead.
/usr/local/bin/crew:1948:
Expand
-
Architecture:
x86_64(x86_64) -
Processor vendor:
GenuineIntel -
User space:
64-bit -
Chromebrew Kernel version:
6.6 -
Chromebrew Running in Container:
false -
Chromebrew version:
1.56.8 -
Chromebrew prefix:
/usr/local -
Chromebrew libdir:
/usr/local/lib64 -
Last update in local repository: a60604b4a
AutoBuild: updates-2025-01-23-00-18 started at 2025-01-23-00UTC (#11177) (3 days ago) -
OS variant:
Chrome OS -
OS version:
hatch-release/R125-15853.61.0 -
OS channel:
stable-channel
Additional context Add any other context about the problem here.
What I think needs to be done:
- [ ] step one
- [ ] step two
Flatpak is currently broken. PRs to fix it are welcome!
seemed to figure out why flatpak doesn't work on ChromeOS (maybe this is just me) When I launched an app using flatpak, I saw
bwrap: No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'.
error: ldconfig failed, exit status 256
ran this under crouton
@lucasgabmoreno @buhron: Just curious. What specifically does flatpak offer that is missing from native Chromebrew packages that you are trying to install?
@lucasgabmoreno @buhron: Just curious. What specifically does flatpak offer that is missing from native Chromebrew packages that you are trying to install?
Packages I need: Onlyoffice, steam, vlc, librewolf, betterbird, doplhin Possibilities: Flatpak install apps into isolated environment, do not compromise system dependencies and programs, and works faster. You can use any of this apps whitout compiling and distro compatiibilities issues: https://flathub.org/
@lucasgabmoreno: Thank you for the feedback. The works faster part is debatable since Chromebrew packages can be compiled to run natively. We currently have onlyoffice available. I'll have to look into the other apps to see if we can add packages for those. For the record, onlyoffice runs as an appimage.
Dolphin I looked into a while back, it currently doesn't have wayland support and XWayland appears to not work either. There are some PRs waiting to implement wayland support or alternatives, but I think the most likely one to get merged in a feasible timeframe is https://github.com/dolphin-emu/dolphin/pull/13222
Dolphin I looked into a while back, it currently doesn't have wayland support and XWayland appears to not work either. There are some PRs waiting to implement wayland support or alternatives, but I think the most likely one to get merged in a feasible timeframe is dolphin-emu/dolphin#13222
No problem, "caja" is the same.
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release with crew update && yes | crew upgrade, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Chromebrew is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly.