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

RPM OSTree Failure When Layering Steam Atop Vauxite #626

Closed
kayomn opened this issue Aug 11, 2024 · 6 comments
Closed

RPM OSTree Failure When Layering Steam Atop Vauxite #626

kayomn opened this issue Aug 11, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@kayomn
Copy link

kayomn commented Aug 11, 2024

When attempting to layer Steam onto the Vauxite image I get the following error during the staging:

error: Checkout libstdc++-14.2.1-1.fc40.i686: Hardlinking ac/859321dfe787f24d016e20e585da522713d84edbf0f6fb4e021543ece37264.file to __init__.cpython-312.opt-1.pyc: File exists

This is the output of my rpm-ostree status.

● ostree-unverified-image:docker://ghcr.io/ublue-os/vauxite-main:latest
                   Digest: sha256:8d721294a131a562968999d9e2de5457a7bf9fe2d334edc3f407f26a3ccdde2c
                  Version: 40.20240810.0 (2024-08-10T03:13:28Z)
          LayeredPackages: gvfs-smb

Note that the issue persists even after a full rpm-ostree reset, so I do not believe this to be specific to the package I have currently layered. I expect this is also happening with any fresh Vauxite image.

@dosubot dosubot bot added the bug Something isn't working label Aug 11, 2024
@xynydev
Copy link
Member

xynydev commented Aug 11, 2024

Layering Steam is a pretty hard problem with rpm-ostree currently. Bazzite does it, and it works pretty well, but requires some hacks.

If you just want to install it locally and don't want to use Bazzite, I recommend against layering. The Flatpak and bazzite-arch are viable alternatives.

@kayomn
Copy link
Author

kayomn commented Aug 11, 2024

I have encountered a few issues with the Steam flatpak, namely that it doesn't seem to detect devices too well and VR does not work at all.

I am looking into this as an alternative - are these hacks that Bazzite had to perform as a work-around documented anywhere?

@xynydev
Copy link
Member

xynydev commented Aug 11, 2024

I'm not aware of there being much documentation. This is the RUN step that installs Steam for Bazzite (among other things): https://github.com/ublue-os/bazzite/blob/main/Containerfile#L421

If you really want to layer Steam, doing it locally will be even more of a headache.

@l33tllama
Copy link

Sadly this is the reason I have to use another distro, as the Steam SDK doesn't seem to work in games outside of Steam (game development) with the Steam flatpak..

@RoyalOughtness
Copy link
Contributor

FYI with negativo, I've had better luck with local layering so far

Copy link

dosubot bot commented Feb 7, 2025

Hi, @kayomn. I'm Dosu, and I'm helping the Main Repos team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • The issue involves a file hardlinking error with libstdc++ when layering Steam onto the Vauxite image using RPM OSTree.
  • @xynydev suggests using alternatives like Flatpak or Bazzite due to the challenges of layering Steam.
  • You noted issues with device detection and VR in the Steam Flatpak.
  • @l33tllama shares similar frustrations with the Steam SDK's limitations in the Flatpak.
  • @RoyalOughtness mentions better success with local layering using negativo.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of the Main Repos repository. If so, you can keep the discussion open by commenting on the issue.
  • Otherwise, the issue will be automatically closed in 14 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Feb 7, 2025
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 21, 2025
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants