Hello @Seek4samurai, can you check what files are listed in ~/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs* (or maybe ~/.steam/debian-installation/ubuntu12_32/steam-runtime/pinned_libs* if you're using the distro-modified Steam package), then delete the pinned_libs* folders so that Steam regenerates them the next time it is started.
Hello @Seek4samurai, can you check what files are listed in
~/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs*(or maybe~/.steam/debian-installation/ubuntu12_32/steam-runtime/pinned_libs*if you're using the distro-modified Steam package), then delete the pinned_libs* folders so that Steam regenerates them the next time it is started.
I tried it already, after I read an issue, where someone had a kind of same problem...
Please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
Please copy your system information from Steam (
Steam->Help->System Information) and put it in a gist, then include a link to the gist in this issue report.
https://gist.github.com/Seek4samurai/e3574056f3bb9dd00b6e39bee667e4a7 This is the link to Gist. Hope you were asking about this.
Facing the same issue on Linux Mint 21. No change if pinned Libs are deleted.
https://gist.github.com/NZRDT1/8985448d92d3c51b5ad12bf81c4653a5
Same issue in Ubuntu 22.10, but in my case deleting all the pinned libs folders fixed the issue.
~/.steam/steam/ubuntu12_32/steam-runtime/pinned_libs_32/
~/.steam/steam/ubuntu12_32/steam-runtime/pinned_libs_64/
~/.steam/steam/ubuntu12_64/steam-runtime-heavy/pinned_libs_32/
~/.steam/steam/ubuntu12_64/steam-runtime-heavy/pinned_libs_64/`
This has been happening to me on and off for a while now, and deleting the pinned libs folders didn't really help.
I figured out that it happens because Steam sometimes doesn't pin libgtk-x11.
To fix it, for an installation in ~/.steam/debian-installation/:
ln -s ~/.steam/debian-installation/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 ~/.steam/debian-installation/ubuntu12_32/steam-runtime/pinned_libs_32/libgtk-x11-2.0.so.0
Similarly for ~/.local/share/Steam:
ln -s ~/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 ~/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libgtk-x11-2.0.so.0
Presumably this will need to be re-done every time the steam runtime updates (and it doesn't automatically pin it).
@tatokis, @qwertychouskie: Please can you add your system information? It would be useful to get a better picture of which operating system versions and which desktop environments are affected by this.
Also, a question for everyone affected by this: assuming you're all using something Debian-based (Debian, Ubuntu, Mint), what does this command output?
dpkg-query -f '${Package}:${Architecture}\t${Version}\t${Status}\n' -W libgtk2.0-0 libdbusmenu-glib4 libdbusmenu-gtk4 libdbus-1-3
There is a known bug in the 2023-04-04 Steam client beta, and specifically that beta, which has symptoms similar to this. That's #9324, not this bug.
Let's keep this bug for situations like the one the OP reported, where the Steam Runtime was meant to be "pinning" its own copy of the 32-bit libgtk2.0-0, but for whatever reason (I don't understand why yet), that was not successful and the system copy was still used anyway.
@tatokis, @qwertychouskie: Please can you add your system information? It would be useful to get a better picture of which operating system versions and which desktop environments are affected by this.
Also, a question for everyone affected by this: assuming you're all using something Debian-based (Debian, Ubuntu, Mint), what does this command output?
dpkg-query -f '${Package}:${Architecture}\t${Version}\t${Status}\n' -W libgtk2.0-0 libdbusmenu-glib4 libdbusmenu-gtk4 libdbus-1-3
My issue was resolved after deleting the pinned libs folders, so I can't reproduce the issue anymore.
My issue was resolved after deleting the pinned libs folders, so I can't reproduce the issue anymore.
For anyone else who is experiencing a similar symptom: instead of trying to work around it by deleting the pinned_libs_* directories, please rename them to something else (perhaps pinned_libs_32_before_bug_8577 and pinned_libs_64_before_bug_8577). If that workaround is not successful, you can remove the old version.
If that workaround is successful, please help us to diagnose what happened, by replying to this bug report with the contents (ls -l) of each of the old and new pinned_libs_* directories.
I'm hoping we can make the setup script setup.sh get this right more reliably, but we can't do that without an idea of what it's doing wrong at the moment.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
When opening steam it works fine and opening games works fine as well. The Problem is when right clicking on steam icon on the tray, no menu opens. After going through internet research. I tried
STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 steam.After that this showed in terminal.
Steps for reproducing this issue: