Hello @allbombson, can you check if any 32 bit OpenGL application works like glxinfo from an i686 build of mesa-demos? Also, please check if you have the mesa-dri-32bit package installed.
Hello thanks for the response, I do have mesa-dri-32bit and a 64bit build of mesa-demos works, ill hunt down a 32bit one to test asap.
@kisak-valve It seems that a 32bit copy of glxgears works just fine under my root user and steam user.
Thanks for checking. Unfortunately, that rules out the common case for this kind of issue. In general, Steam expects to be run as the same user as the X session, and running Steam as root is not supported. Separately, your sandbox config sounds uncommon and you might be causing an edge case most users would never see.
This is outside my personal experience and I won't be able to help much here, but someone else might have an idea on what to check.
Maybe trying something like cd ~/.local/share/Steam/ubuntu12_32/steam-runtime; ./run.sh ./amd64/usr/bin/steam-runtime-system-info as your steam user would give a hint. Please use a gist instead of copy/pasting a wall of text.
Funny that you say that, as X is actually being run as root. I will try out running it as my steam user in a bit and see if that fixes anything. also the gist as asked https://gist.github.com/allbombson/262efda933c537d19c0a3b18f782aab6 However im unsure if X as root is really the issue here as i run chrome under a diffrent user just fine but i will try it anyway just to see.
Issue remains even under a x session started by the steam user
Kinda looks like the steam runtime failed to get itself setup which started with the first line of that output - Warning: An unexpected error occurred while executing "/sbin/ldconfig -XNv", the exit status was 127.
On all major distros, regular users are able to run that command with those options. Maybe worth checking?
command seems to run fine so i dunno what that is about
In general, Steam expects to be run as the same user as the X session
This. If you want to do privilege-separation, I would recommend creating separate OS-level users (with a separate uid, a separate home directory and a separate X display) and switching between them through the login prompt as though they were different people.
I do this myself: I have a user account for development and general computer use, and a separate, unprivileged user account for running Steam and playing games, and I use GNOME's "Switch User" feature (fast user switching) to switch between them. From the operating system's point of view, it's the same as if I was sharing the computer with another family member.
Steam is not designed to share a home directory or X display with other users of different privilege levels.
Also, if you share an X11 display between different user IDs, there is little or no effective privilege separation between them: a malicious or compromised program running as the Steam user is very likely to be able to take control over programs that are running as your more-privileged user. X11 does not prevent different users sharing a display from spying on each other (screenshots or video capture), does not prevent them from controlling each other's programs (by sending fake input events), and so on. So if you want to gain security against the possibility that a game might be malicious or compromised, you will need to use a separate X11 display anyway.
Warning: An unexpected error occurred while executing "/sbin/ldconfig -XNv", the exit status was 127
If you log in as the Steam user and run /sbin/ldconfig -XNv; echo $?, what output do you get? (Again, use a gist.)
In general, Steam expects to be run as the same user as the X session
To be clearer about this: if you log in as a non-root user, some distributions are designed to run the X server as root and the rest of the session as the user you logged in as. I don't know whether Void Linux is one of these distributions or not.
If that is the way your distribution is designed, then it's OK to do that.
The situation that is not recommended is if you log in to a desktop session as user A (regardless of whether user A is root or not), use su or sudo or similar tools to switch to user B, and run Steam as user B.
Maybe trying something like cd ~/.local/share/Steam/ubuntu12_32/steam-runtime; ./run.sh ./amd64/usr/bin/steam-runtime-system-info as your steam user would give a hint.
From the gist, you seem to have done that in a text-mode login session?
Please log in to your GUI (in gdm or lightdm or sddm or whatever display manager you're using) as the Steam user, and run the command within that GUI session, from a terminal (gnome-terminal, Konsole, xterm or whatever similar program is available).
I notice from the gist that you have two versions of Steam installed: the non-Flatpak version at /usr/bin/steam, and the unofficial Flatpak version from Flathub. Which one are you trying to use?
I like to sandbox all the p rograms I run and then just use my machine as root
Wait, does this mean you are logging in to your desktop GUI session as root?
This is a really bad idea; please don't do it. It makes it very likely that a malicious or compromised program can escalate its privileges to root. It also makes it very likely that a relatively minor bug in a non-malicious program will break your whole system, or that you will break your whole system by making a relatively small mistake.
If you are used to logging into Windows machines as an "Administrator" user, note that this is not equivalent to using root on a Linux machine. The closest equivalent of "Administrator" in Linux is logging in as an ordinary user who has permission to use sudo to escalate privileges to root. In Debian or Ubuntu they would be a member of the sudo group, or in Red-Hat-derived systems they would be a member of the wheel group - I don't know what Void Linux's closest equivalent is, but it probably has something. The closest equivalent of root in Windows is SYSTEM or LOCAL_SYSTEM, and it is not possible to log in to the GUI as those users at all.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
I have installed steam and all dependices I need that I know of. I am also using Intel Intergrated Graphics with all the drivers for it that I know of. After creating a new user called "steam" (I like to sandbox all the p rograms I run and then just use my machine as root) Steam lauches fine and downloads but right about when it should launch and ask for login it shows an error saying glXChooseVisual failed. After hours and hours of googling I cant seem to figure out why. AGAIN I'm using intel not amd or nvidia. The expected results for the program is that it should start and let me login without any issues.
Steps for reproducing this issue: