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

Steam dependency install issue #2556

Closed
3 tasks done
Im-CatDev opened this issue Feb 29, 2024 · 7 comments
Closed
3 tasks done

Steam dependency install issue #2556

Im-CatDev opened this issue Feb 29, 2024 · 7 comments
Labels
User Error Issue is due to user error and not a bug with pi-apps

Comments

@Im-CatDev
Copy link

Confirmations

What happened?

Steam can't install dependecies

Description

When i try to launch steam from my desktop, a terminal window asking to download additional packages, when i press enter, a bunch of errors are being thrown. Logs below

What are your system specs (run the following command in your terminal)?

OS: Debian GNU/Linux 12 (bookworm)
OS architecture: 64-bit
Last updated Pi-Apps on: 02/29/2024
Latest Pi-Apps version: 02/29/2024
Kernel: aarch64 6.1.0-rpi8-rpi-v8
Device model: Raspberry Pi 5 Model B Rev 1.0
SOC identifier: bcm2712
Cpu name: Cortex-A76
Ram size: 7.94 GB
Raspberry Pi OS image version: 2023-12-05
Language: en_US.UTF-8

(Recommended) Error log? Terminal output? Debug messages?

Steam needs to install these additional packages:
libc6:arm64 libc6:i386 libegl1:arm64 libgbm1:arm64 libgl1-mesa-dri:arm64 libgl1-mesa-dri:i386 libgl1:arm64 libgl1:i386 steam-libs-amd64:amd64 steam-libs-i386:i386 xterm

Press return to proceed with the installation: 
.............
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package libc6:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  libc6-dev libnss-nis libnss-nisplus libcrypt1 libc6-dev:armhf libnss-nis:armhf libnss-nisplus:armhf libcrypt1:armhf

Package libgl1:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libgl1-mesa-dri:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libc6:i386' has no installation candidate
E: Package 'libgl1-mesa-dri:i386' has no installation candidate
E: Package 'libgl1:i386' has no installation candidate

Press return to continue:
@Im-CatDev Im-CatDev added the bug Something isn't working label Feb 29, 2024
@theofficialgman
Copy link
Collaborator

When i try to launch steam from my desktop

delete the steam file from your desktop and then reboot. afterwards it should launch without errors

you neglected to follow the warning displayed "YOU NEED TO REBOOT before starting steam. This is because Steam is the first application on your system to be installed into the /usr/local folder." since you did not have a /usr/local folder prior to installing steam

@theofficialgman theofficialgman closed this as not planned Won't fix, can't repro, duplicate, stale Mar 8, 2024
@theofficialgman theofficialgman added User Error Issue is due to user error and not a bug with pi-apps and removed bug Something isn't working labels Mar 8, 2024
@Im-CatDev
Copy link
Author

When i try to launch steam from my desktop

delete the steam file from your desktop and then reboot. afterwards it should launch without errors

you neglected to follow the warning displayed "YOU NEED TO REBOOT before starting steam. This is because Steam is the first application on your system to be installed into the /usr/local folder." since you did not have a /usr/local folder prior to installing steam

I rebooted as the console told me to, but no one said to delete the desktop file

@Botspot
Copy link
Owner

Botspot commented Mar 8, 2024

This situation confuses me.
Installing steam should not leave behind a launcher on the Desktop. Such a file is explicitly removed by pi-apps at the end of installation:

rm -f $HOME/Desktop/steam.desktop

what I don't understand is: How was the steam.desktop file still there after a reboot?

@Im-CatDev
Copy link
Author

This situation confuses me. Installing steam should not leave behind a launcher on the Desktop. Such a file is explicitly removed by pi-apps at the end of installation:

rm -f $HOME/Desktop/steam.desktop

what I don't understand is: How was the steam.desktop file still there after a reboot?

Sorry, I made a mistake, I meant I tried to start it from the taskbar thing

@theofficialgman
Copy link
Collaborator

This situation confuses me. Installing steam should not leave behind a launcher on the Desktop. Such a file is explicitly removed by pi-apps at the end of installation:

rm -f $HOME/Desktop/steam.desktop

what I don't understand is: How was the steam.desktop file still there after a reboot?

installation of the steam deb installs a .desktop file in /usr/share/applications/steam.desktop. Running steam copies that .desktop file to ~/Desktop/steam.desktop. unfortunately, both of these files hardcode the location of the steam binary Exec=/usr/bin/steam. If the user DOES NOT HAVE .desktop files existing in /usr/local/share/applications at the time of DE LOGIN, then that directory NEVER gets searched for new .desktop files. That is why the reboot is critical for users where this is the first application in /usr/local/share/applications.

IF they do NOT reboot, then launching steam through the applications menu, then it will run /usr/share/applications/steam.desktop which calls /usr/bin/steam which will result in the errors posted in the first message here. Additionally, it will also copy that .desktop file to ~/Desktop/steam.desktop. Now if the user reboots it doesn't matter that /usr/local/share/applications is searched, because ~/Desktop has priority over all other locations. So they will NEVER get our custom steam.desktop file in /usr/local/share/applications unless they manually delete the one on their desktop. This is why its critical to read and follow directions.

@theofficialgman
Copy link
Collaborator

I have already explained this before multiple times. As mentioned, the best way to workaround how DEs search the XDG paths based on what is available at login is to use dpkg-divert as described here #2555 (comment)

@Im-CatDev
Copy link
Author

I will update you when something changes, at the moment my pi broke :( so it may take a while

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
User Error Issue is due to user error and not a bug with pi-apps
Projects
None yet
Development

No branches or pull requests

3 participants