protonscr

Store, Community Black Screen

steamopen reviewedruntime
ValveSoftware/steam-for-linux#4553 · opened 2016-07-16 by ghost · updated 2019-06-21 · 14 comments · github
1 matching comments, n / p to jump
?ghost 2016-07-16 github

Your system information

  • Steam client version: Steam isn't telling me the version, but I have tried the latest stable and steam beta clients.
  • Distribution (e.g. Ubuntu): Ubuntu 16.04
  • Opted into Steam client beta?: [Yes/No] Yes, but issue affected non-beta client.
  • Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Keep in mind I am running the Mesa 12.1 Open-Source AMD Drivers.

I expect when I launch steam to be taken to the Store page and have the normal content appear. But when I open it in Ubuntu 16.04, the UI (Store, Library, Community) etc show up fine. But the actual content where the store should be is a black screen.

The only 'tab' that shows up properly is my library. So I can play games I have, but I can't go out to the store and buy new games, for example.

Here is an image of my problem, my account names/info are blocked out: Imgur Link

Lastly, here is my console output when I launch steam from there, looks normal to me:

`Running Steam on ubuntu 16.04 64-bit
STEAM_RUNTIME is enabled automatically
[2016-07-16 14:51:17] Startup - updater built Jul 12 2016 21:46:20
[2016-07-16 14:51:17] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
[2016-07-16 14:51:17] Verifying installation...
[2016-07-16 14:51:17] Verification complete
Unable to remove /home/liam/.steam/CONFIG/SteamAppData.vdf!

Running Steam on ubuntu 16.04 64-bit
STEAM_RUNTIME has been set by the user to: /home/liam/.steam/ubuntu12_32/steam-runtime

`

Steps for reproducing this issue:

  1. Launch Steam
  2. Issue with black screen should be pretty obvious from there.
Ggdrewb-valve maintainer 2016-07-16 github

There are many reported issues here with 16.04, you might want to check through and see if any of those workarounds.

?ghost 2016-07-17 github

Decided to go on a whim and install Linux Mint 18 Cinnamon (Based off of Ubuntu 16.04) and that is displaying the steam store, community pages etc just fine.

How odd.

Nnukeop 2016-07-23 github

I keep seeing this problem all the time. Sometimes it will work for a while after restarting the system completely, then without warning it stops displaying any pages, just pretending to be loading them forever.

The GNU/Linux client is an embarrassing mess, and considering that Valve is pushing steam machines which run GNU/Linux, there is startlingly little being done to address these numerous issues.

Nnullsystem 2016-07-24 github

I pretty much had this problem as well (can't use the steam browser, can still play games), still can't find a solution especially when I run: steam --reset, it just said:

Error: Couldn't find bootstrap, it's not safe to reset Steam. Please contact technical support.

I'm using Debian Unstable/Sid amd64, using the non-beta client, and using nvidia proprietary driver.

Image for proof: Imgur Link

Ssizeofbool 2016-08-07 github

I have same trouble. Some pages show up as black and empty while viewing their source text. I can open them through any browser just fine.
Specs: GNU\Linux Debian 8 'jessie' x86_64 with Xfce

view_of_store_page
source_of_store_page
view_of_account_details_page
source_of_account_details_page
view_of_steam_guard_settings_page

Log don't give any clues:

Running Steam on debian 8 64-bit
STEAM_RUNTIME has been set by the user to: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime
ExecCommandLine: "/home/user/.local/share/Steam/ubuntu12_32/steam steam://open/driverhelperready"
ExecSteamURL: "steam://open/driverhelperready"
Generating new string page texture 203: 48x256, total string texture memory is 2.72 MB
Generating new string page texture 204: 256x256, total string texture memory is 2.98 MB
Generating new string page texture 207: 16x256, total string texture memory is 3.00 MB
Generating new string page texture 208: 512x256, total string texture memory is 3.52 MB
Generating new string page texture 209: 64x256, total string texture memory is 3.59 MB
Generating new string page texture 212: 256x256, total string texture memory is 3.85 MB
Generating new string page texture 214: 128x256, total string texture memory is 3.98 MB
Generating new string page texture 215: 256x256, total string texture memory is 4.24 MB
Installing breakpad exception handler for appid(steam)/version(1469850758)
Installing breakpad exception handler for appid(steam)/version(1469850758)
ExecSteamURL: "steam://url/StoreAccount"
ExecSteamURL: "steam://url/SteamIDMyProfile"
ExecSteamURL: "steam://url/StoreAccount"
ExecSteamURL: "steam://url/StoreAccount"
ExecSteamURL: "steam://url/StoreAccount"
ExecSteamURL: "steam://url/StoreAccount"
Generating new string page texture 242: 256x256, total string texture memory is 393.22 KB
Generating new string page texture 250: 64x256, total string texture memory is 4.31 MB
Generating new string page texture 251: 48x256, total string texture memory is 4.36 MB
ExecSteamURL: "steam://url/ManageSteamGuard"
ExecSteamURL: "steam://url/SteamClientBetaBugReports"

Pp-snft 2016-08-12 github

Let me add, that also the advertisements at Steam's startup are black. (I am on Debian GNU\Linux testing/stretch amd64 with Gnome and radeon mesa driver.)

Sstuartdb 2016-08-13 github

I was also experiencing this issue on Debian Testing/Stretch x86-64, but in my case, the error log was helpful, I had a number of these entries when attempting to load :

/home/stuart/.steam/ubuntu12_32/steamwebhelper: error while loading shared libraries: libgpg-error.so.0: cannot open shared object file: No such file or directory

In Debian, libgpg-error is provided by the libgpg-error0 package. You can check if you have the library installed:

find /lib -name *libgpg-error*

Chances are, if you're running a x86-64 version of debian, you'll already have the x86-64 version of the package:

/lib/x86_64-linux-gnu/libgpg-error.so.0.19.1
/lib/x86_64-linux-gnu/libgpg-error.so.0

But Steam requires the x86 package. If you're already running the steam client, you would have already enabled multi-arch and installed a bunch of related packages, so you should be able to solve this with:

sudo apt install libgpg-error0:i386

Then check again:

[stuart@copper ~]$ find /lib -name *libgpg-error*
/lib/i386-linux-gnu/libgpg-error.so.0.19.1
/lib/i386-linux-gnu/libgpg-error.so.0
/lib/x86_64-linux-gnu/libgpg-error.so.0.19.1
/lib/x86_64-linux-gnu/libgpg-error.so.0

Now the store and community pages load without incident.

Hopefully this also help @p-snft @sizeofbool and @grillmaster-t28 who mentioned they are also running Debian x86-64.

Ssizeofbool 2016-08-13 github

@Plagman @gdrewb-valve Since latest Steam Client Beta update, I have no problems mentioned earlier.
Advertisement window, Steam account details page, Steam Guard settings page, Steam Community Forums, all is working now as expected.
Looks like latest update fixed it.
Current Steam version:
steam_version

Ggdrewb-valve maintainer 2016-08-13 github

@LPH24 , are you still having problems?

Pp-snft 2016-08-14 github

@stuartdb That one helped, thanks.

Hhillcjames 2018-01-31 github

In case it helps anyone else, after a recent steam update I had a very similar-looking issue (black screen at store and community tabs on linux mint 17.1, not run under wine), which was solved by reinstalling libnss3:

sudo apt-get install --reinstall libnss3

https://github.com/adieuadieu/serverless-chrome/issues/53

Found by running steam in terminal and looking through error messages.

Kkisak-valve maintainer 2018-01-31 github

Hello @nukeop, please try to keep you comments civilized.

To answer your question, libnss's libraries do not follow common naming practices used by most other system libraries and #5311 is tracking the issue with Steam's library pinning logic.

AArthurGibbs 2018-02-10 github

Thanks @hillcjames this fixed it for me.

Eeuronay 2018-06-29 github

I had the same problem and @hillcjames solution fixed it. Ubuntu 16.04.

Nothing extracted yet.