-
Notifications
You must be signed in to change notification settings - Fork 43
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
bwrap: creation of new user namespaces was not disabled as requested #38
Comments
Are you still running into this issue? If so, can you provide the steps you take when you attempt to launch the game. |
Hi! the same bug seems to persist on Ubuntu 22.10.
however, ubuntu 23.04 has solved the issue, so i guess its not needed to fix since 22.10 is not an LTS release? |
This is almost certainly an issue with Ubuntu's halfhearted support of flatpaks. Bwrap (bubblewrap) is one of the programs used to create a flatpak container. |
i can imagine, thats why its interesting that it does run on LTS and 23.04 for some reason. im glad though that its not affecting the current "stable" releases, as people should move away from 22.10 afaik. i dont personally follow ubuntu development too much, but since quite a few of my friends want to start using linux, most of them picked ubuntu... |
Got this today myself. Arch Linux Downgrading to 1.15.4 works, though. |
Seems like this is related to #97 |
This issue has been resolved with a workaround. Users using XIVLauncher and Steam together should now use the XLM compatibilitytool to launch instead of Flatpak. The old method of launching XL is now unsupposed. |
Hi!
Relevant System Specs:
OS: Ubuntu 22.10
Flatpak Version: 1.15.4
when using XIVLauncher (as Flatpak from Flathub) in combination with Steam (installed as a deb), following the advice from here: https://goatcorp.github.io/faq/steamdeck.html it happens to not work as it should on Ubuntu. (Adding the game as a Non-Steam Game)
it always ends up with the message as stated in the title.
It does however work on nobara, arch, and nixOS (as i already cycled through these distros while playing the game)
is there something i might have missed, and someone is able to give me a pointer to what i can do to "fix" this behaviour?
if there is anything (such as logs) which might help determine the issue, let me know and i will send them your way.
Thanks in advance!
The text was updated successfully, but these errors were encountered: