steam-for-linux
steam-for-linux copied to clipboard
ValveSoftware
unable to access game properties
Your system information: https://gist.github.com/mathew2214/729fc6d2bb0becc52dbf545d55269197
- Steam client version (build number or date): dec 20 2020 23:07:25
- Distribution (e.g. Ubuntu): Debian 11
- Opted into Steam client beta?: [Yes/No] yes
- Have you checked for system updates?: [Yes/No] yes
Steps to reproduce: right click on a game in steam library, and click on "Properties"
expected result: properties window opens
observed bugged result: nothing happens, no errors or anything.
this was certainly a bug introduced in the most recent update. as the previous build had no issues.
Hello @mathew2214, just to confirm, does this happen with all games or some games?
@kisak-valve this happens with every game in my library. the most recent update must've done some change to the properties button and broken it. reverting to the stable client does not fix this. so i dont think its a bug specific to the beta client.
is there a way to revert to the previous beta as a means to access my game's properties until a proper fix is made?
i have discovered that switching to big picture mode will allow me to change my games' properties. very annoying, but it works.
I suspect this is specific to @mathew2214's setup in some way. Unless we see other folks able to reproduce on Debian.
update: several steam beta updates have passed. and this bug has yet to be fixed by valve. its getting rather annoying to have to open big picture, navigate to my game, change a setting, and then close big picture, any time i want to change something.
UPDATE: i have discovered that removing the "-no-browser" from steam's switches allows me to access the game properties without the use of big picture. however, doing this also completely ruins the performance, stability, and aesthetics of the steam client. so it looks like im stuck using big picture to change my games' properties.
Passing -no-browser is unsupported and will likely disable more and more essential functionality moving forward. The Steam client UI is progressively migrating to using "web" tech exclusively.
Could this be reconsidered? CEF is a massive ressource hog which often causes multiple gigabytes of memory usage by the steamwebhelper alone and therefore the Steam client to have a larger memory footprint than many games launched through it.
CPU usage is also through the roof with 10-15% CPU usage with web rendering functionalities enabled and 0.2% with them disabled. Could at least something like a launch argument to get the legacy UI back or a proper Steam minimal client (which offers just installing/launching games as well as the legacy chat) be considered?
@UFeindschiff passing "-no-browser +open steam://open/minigameslist" almost works for that. the only things that dont work are uninstalling a game, and changing properties.
still not fixed as of July 2021. given how much performance will need to be squeezed from the Steam Deck's advertised specs, i hope the browserless mode gets fixed by then.
I do have the exact same problem on Ubuntu 20.04. Big Picture mode lets me do the properties, everything else is partially broken/not showing -- including the store! This bug makes Valve lose money as I cannot buy anything on steam.
Hello @mwweissmann, you've described a general issue with libcef (Steam's web component) failing to start. Please open a new issue report.
As of today's update, I am experiencing same issue (no properties) without the no-browser. Also on Debian Bookworm.
Same issue, started after the update. Reinstalling Steam did not help. Debian Bookworm as well.
I cannot use the context menus of various kinds in the steam client under Fedora 38, Gnome, with nvidia drivers. Basically I can open context menus but can't (usually) click anything in them. The click tends to "fall through" the menu and hit whatever is underneath. I cannot for instance enable the steam beta, because that's in a context menu of sorts in the settings.
I can access these menus by using the big picture mode, however.
This also affects me, unable to access any game's properties in my library.
I also have this issue; only able to use the laggy & inconvenient big picture mode to access any game properties menu.
Also seeing this. Right click on game in my lib, click properties....and nothing pops up. Running Ubuntu 23.04 on Wayland.
It seems that the issue is quite common-spread. I would like very much to see it resolved - is there something specific that can be done from our side, to help the debugging?
@Cat-Lady we (Valve devs) are more likely to look at an issue if it's a fresh report instead of a necro bump of an old -no-browser problem. I see Wayland mentioned .. is this Wayland specific?
same issue on Ubuntu 22.04.2
Im using x11 and the latest beta update of steam. To clarify, the properties popup menu cannot be accessed for any game (or anything from the gear icon menu) unless using big picture mode
@Cat-Lady we (Valve devs) are more likely to look at an issue if it's a fresh report instead of a necro bump of an old
-no-browserproblem.
I would post it as a fresh issue, but it is, already, choke-full of fresh reports. I guess someone with proper rights can split/rename/whatever the issue.
I see Wayland mentioned .. is this Wayland specific?
All details are in the reports - it affects both X and wayland, and is encountered by people using wide range of distributions.
There is a new setting Enable context menu focus compatibility mode in Settings -> Interface with latest beta client. Does this have any impact on your issue?
Update:
@TTimo See issue here: https://github.com/ValveSoftware/steam-for-linux/issues/9273#issuecomment-1627703608
Second-level menus are not fixed by the compatibility mode.
