Support us on Patreon
PayPal
It seems that the big Steam update, which rolled out on December 12th disabled support for the Steam Web Browser for 32-bit distributions. Steam also no longer supports 32-bit Linux distributions.
The change wasn't listed explicitly in the client update notes, but the official Steam Knowledge Base Article has been updated to clearly list that 32-bit Linux distributions are no longer supported:
Users running on 32-bit Linux distributions will see "The Steam Browser is disabled" message when they try to access the Steam Store, overlay web browser, achievement pages or other Steam functions that open a web browser through the client, and will have to use a standalone browser to access these features now.
Other features that do not depend on the built-in browser (like Steam friends, game invites and at least part of big picture mode) are unaffected by the change.
Since the vast majority of GOL users seem to be running a 64-bit distribution on their gaming machine, most will not experience the difference, but here's the reminder for the two remaining users.
However, since all the missing functionality (aside from using the browser in the overlay) can be mitigated by logging into your Steam account in a regular desktop browser, the lack of the feature is limited to an annoyance (hopefully Valve will think about simply allowing launching games from the store) and hopefully this is a sign of a true 64-bit Steam client for Linux.
Note: Article cleaned up for publishing by liamdawe. Article taken from GamingOnLinux.com.
The change wasn't listed explicitly in the client update notes, but the official Steam Knowledge Base Article has been updated to clearly list that 32-bit Linux distributions are no longer supported:
QuoteLinux
32-bit Linux distributions are also no longer supported. Please install a 64-bit Linux distribution to make use of the Steam browser.
Users running on 32-bit Linux distributions will see "The Steam Browser is disabled" message when they try to access the Steam Store, overlay web browser, achievement pages or other Steam functions that open a web browser through the client, and will have to use a standalone browser to access these features now.
Other features that do not depend on the built-in browser (like Steam friends, game invites and at least part of big picture mode) are unaffected by the change.
Since the vast majority of GOL users seem to be running a 64-bit distribution on their gaming machine, most will not experience the difference, but here's the reminder for the two remaining users.
However, since all the missing functionality (aside from using the browser in the overlay) can be mitigated by logging into your Steam account in a regular desktop browser, the lack of the feature is limited to an annoyance (hopefully Valve will think about simply allowing launching games from the store) and hopefully this is a sign of a true 64-bit Steam client for Linux.
Note: Article cleaned up for publishing by liamdawe. Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
I have a couch living room media center PC. It's an Atom+Nvidia+2GB RAM. If the system would be 32bit and Steam would decide that I can't run the client+games anymore, I couldn't play those games in my living room anymore - as well as I couldn't use this PC for in home streaming within steam. It's perfectly capable of this and you don't need fancy bits or anything to receive a stream and display it.
Steam should at least somewhat support 32bit for a rather long time. I don't think I want to replace some of my systems with newer ones and generate electronic garbage for no actual benefit. It still works just fine for it's job.
Can't say anything about the official Chromium team's support though, but at least it works fine :)
It happened to Mac OSX Snow Leopard users. Suddenly their Steam client updated and bam! no longer ran in their system.
People opened threads on Steam's Community forums about this, but since in Apple's world when there is a new something you ditch the old one and buy the new one they weren't "that many" (in comparison), their petitions weren't heard.
You're right, it looks like CEF still has 32 bit builds, so this is Valve's decision alone. Only MAC has 64 bit only:
http://opensource.spotify.com/cefbuilds/index.html
Of course if it weren't for Doze 32 bit would have been dead for several years already.
I have 32-bit and you still have access to your library from the client so I can still play the games i bought, as long as the game is for 32-bit. Another interesting note is that you can install games from the steam website through the client so its not that bad. I totally agree on your last paragraph.
Last edited by rambo1462 on 17 December 2016 at 10:14 pm UTC
Unable to open local device: 0001:000b:01No matter if it is a headset or the steam controller. So the steam controller can't work any more. I've installed the package steam-devices. My /lib/udev/rules.d/99-steam-controller-perms.rules:
# Valve USB devicesSUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
# Steam Controller udev write access
KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess"
# HTC Vive HID Sensor naming and permissioning
I've a 64 Bit system (i7 6700k).
EDIT: I don't know if this has something to do with this update. At the moment I don't know what the problem is. My Controller runs perfectly on a older steam client on the same system.
Last edited by 1xok on 18 December 2016 at 12:44 am UTC
For some reason my rules ended up getting copied there and that copy overrides the one in /lib/udev/.
I've found a solution. Under Ubuntu the rules which came with the steam-devices package are just incomplete. This works for me:
http://askubuntu.com/questions/686214/how-do-i-get-a-steam-controller-working
Last edited by 1xok on 19 December 2016 at 8:46 pm UTC
Get real, people. 32-bit is bad enough on Windows, but on Linux you dive into dependency hell when you dawdle in 32-bit. It's bad. Official Steam support for 32-bit systems should be cancelled. 64-bit is the only way to progress OS and game development in the modern era.
Not to mention there's little excuse. I've seen people in this thread posing the question "What happens to 32-bit users?"
They upgrade. If you're running 32-bit, you're probably not running any games anyway. You can get an quad core amd64 CPU for $75 USD, and a motherboard to go with it for $60 USD. And that's not even on sale.
Really, almost nobody should run 32-bit anymore. 64-bit is affordable and objectively superior.
The ONLY argument for 32-bit support is for legacy software. Most of that can be run on amd64 systems anyway.
I do think it should be an option to download 32-bit distros or some other sort of i386 toolset to compile 32-bit code, but beyond that, 32-bit is useless.
I agree on the fact that support for 32 bits should be dropped, but it would be nice if it was somehow still possible for me to play Half-Life 1 and others on my old crappy laptop. SteamCMD or equivalent should be enough for this purpose.