Bug#954960: steam: new steam update crashes with fatal error: could not load steamui.so

2020-03-26 Thread Simon McVittie
On Thu, 26 Mar 2020 at 22:32:25 +, Ximin Luo wrote:
> Thanks for the hints. I was able to figure out that somehow I had an
> extra copy of an old glib from May 2018 in /lib, similar to the problem
> described in #896019.

Ugh, it's looking like this is more common than we might have
anticipated...

> sudo rm -f /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4

That's GLib 2.32.4, from Debian 7 'wheezy' (or Ubuntu 12.04 'precise',
or some contemporary version), 2012 or early 2013.

Do you have any idea why it might still be there, even after you
(presumably) upgraded libglib2.0-0:i386 to a much newer version?

Or, do you have any ideas of something significant that might have
happened to this system in May 2018, like disk corruption, encountering
dpkg bugs, applying local workarounds for wrong library dependencies,
that sort of thing?

Do you have any other non-dpkg-owned libraries in /lib/MULTIARCH or in
/usr/lib/MULTIARCH?

I wonder whether it's significant, or just coincidence, that this is the
same GLib version that's in the Steam Runtime?

smcv



Bug#954960: steam: new steam update crashes with fatal error: could not load steamui.so

2020-03-26 Thread Ximin Luo
Control: notfound -1 1.0.0.61-2
Control: done -1

Hi,

Thanks for the hints. I was able to figure out that somehow I had an extra copy 
of an old glib from May 2018 in /lib, similar to the problem described in 
#896019. After removing it:

sudo rm -f /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4

steam is now back to normal and I don't need that workaround any more.

Ximin

Simon McVittie:
> On Wed, 25 Mar 2020 at 20:48:37 +, Ximin Luo wrote:
>> In $STEAMDIR/error.log we see:
>>
>> Failed to load steamui.so - dlerror(): 
>> /usr/lib/i386-linux-gnu/libpango-1.0.so.0: undefined symbol: 
>> g_log_structured_standard
> 
> It looks as though the Steam Runtime infrastructure is selecting libpango
> from your host OS (Debian), but GLib from the Steam Runtime. That shouldn't
> be happening: it is meant to use the host OS (i.e. Debian) version of GLib
> if it's newer, which, in practice, it has been for a long time.
> 
> Recent versions of Steam have a debugging tool that can be used to
> diagnose issues like this. It's intended for upstream to use, but should
> be equally handy for downstreams like us. (You'll find my name in its
> changelog - I have both of those hats right now.)
> 
> Please try running:
> 
> ~/.steam/steam/ubuntu12_32/steam-runtime/run.sh \
> 
> ~/.steam/steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-system-info
> 
> It will output quite a lot of JSON. Please send it to this bug report
> (you can censor it if you want, as long as it's clear which bits you have
> edited).
> 
> It might also help to re-run the same tool with the --verbose option,
> which will list the paths to all the libraries that are part of the
> Steam Runtime.
> 
> You could also try running
> 
> ~/.steam/steam/ubuntu12_32/steam-runtime/setup.sh --force
> 
> but if you do, please capture a steam-runtime-system-info report before
> and after you do that, so we can compare.
> 
>> Launching /usr/games/steam with STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0
>> works around this problem for now.
> 
> That option usually breaks the open-source (Mesa) driver stack by using
> the Steam Runtime's ancient libraries in preference to the ones Mesa
> needs, so it is generally a bad idea, and it will disappear entirely in
> the next release of the Steam Runtime. I'm surprised it's having a
> positive effect for you.
> 
> smcv
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git



Bug#954960: steam: new steam update crashes with fatal error: could not load steamui.so

2020-03-26 Thread Simon McVittie
On Wed, 25 Mar 2020 at 20:48:37 +, Ximin Luo wrote:
> In $STEAMDIR/error.log we see:
> 
> Failed to load steamui.so - dlerror(): 
> /usr/lib/i386-linux-gnu/libpango-1.0.so.0: undefined symbol: 
> g_log_structured_standard

It looks as though the Steam Runtime infrastructure is selecting libpango
from your host OS (Debian), but GLib from the Steam Runtime. That shouldn't
be happening: it is meant to use the host OS (i.e. Debian) version of GLib
if it's newer, which, in practice, it has been for a long time.

Recent versions of Steam have a debugging tool that can be used to
diagnose issues like this. It's intended for upstream to use, but should
be equally handy for downstreams like us. (You'll find my name in its
changelog - I have both of those hats right now.)

Please try running:

~/.steam/steam/ubuntu12_32/steam-runtime/run.sh \

~/.steam/steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-system-info

It will output quite a lot of JSON. Please send it to this bug report
(you can censor it if you want, as long as it's clear which bits you have
edited).

It might also help to re-run the same tool with the --verbose option,
which will list the paths to all the libraries that are part of the
Steam Runtime.

You could also try running

~/.steam/steam/ubuntu12_32/steam-runtime/setup.sh --force

but if you do, please capture a steam-runtime-system-info report before
and after you do that, so we can compare.

> Launching /usr/games/steam with STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0
> works around this problem for now.

That option usually breaks the open-source (Mesa) driver stack by using
the Steam Runtime's ancient libraries in preference to the ones Mesa
needs, so it is generally a bad idea, and it will disappear entirely in
the next release of the Steam Runtime. I'm surprised it's having a
positive effect for you.

smcv



Bug#954960: steam: new steam update crashes with fatal error: could not load steamui.so

2020-03-25 Thread Ximin Luo
Ximin Luo:
> Ximin Luo:
>> Package: steam
>> Version: 1.0.0.61-2
>> Severity: important
>>
>> Dear Maintainer,
>>
>> The latest Steam client upgrade fails to run, crashing with a dialog box 
>> saying:
>>
>>Fatal Error: Failed to load steamui.so
>>
>> There's no other details unfortunately.
>>
> 
> In $STEAMDIR/error.log we see:
> 
> Failed to load steamui.so - dlerror(): 
> /usr/lib/i386-linux-gnu/libpango-1.0.so.0: undefined symbol: 
> g_log_structured_standard
> 
> Launching /usr/games/steam with STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 works 
> around this problem for now.
> 

I spoke a little too soon. steam launches but the main content panels are all 
black. However, "Big Picture" (full screen) mode works - right click the steam 
tray icon and select "Big Picture".

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git



Bug#954960: steam: new steam update crashes with fatal error: could not load steamui.so

2020-03-25 Thread Ximin Luo
Ximin Luo:
> Package: steam
> Version: 1.0.0.61-2
> Severity: important
> 
> Dear Maintainer,
> 
> The latest Steam client upgrade fails to run, crashing with a dialog box 
> saying:
> 
>Fatal Error: Failed to load steamui.so
> 
> There's no other details unfortunately.
> 

In $STEAMDIR/error.log we see:

Failed to load steamui.so - dlerror(): 
/usr/lib/i386-linux-gnu/libpango-1.0.so.0: undefined symbol: 
g_log_structured_standard

Launching /usr/games/steam with STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 works 
around this problem for now.

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git



Bug#954960: steam: new steam update crashes with fatal error: could not load steamui.so

2020-03-25 Thread Ximin Luo
Package: steam
Version: 1.0.0.61-2
Severity: important

Dear Maintainer,

The latest Steam client upgrade fails to run, crashing with a dialog box saying:

   Fatal Error: Failed to load steamui.so

There's no other details unfortunately.

Best,
Ximin

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable'), (300, 'unstable'), (100, 'experimental'), 
(1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages steam depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libc6  2.30-2
ii  libgl1-mesa-dri19.3.3-1
ii  libgl1-mesa-glx19.3.3-1
ii  libgpg-error0  1.37-1
ii  libstdc++6 10-20200312-2
ii  libudev1   244.3-1
ii  libx11-6   2:1.6.9-2
ii  libxcb-dri3-0  1.13.1-5
ii  libxinerama1   2:1.1.4-2
ii  xz-utils   5.2.4-1+b1

Versions of packages steam recommends:
ii  ca-certificates   20190110
ii  fontconfig2.13.1-2+b1
ii  fonts-liberation  1:1.07.4-11
ii  gnome-terminal [x-terminal-emulator]  3.36.0.1-1
ii  libxss1   1:1.2.3-1
ii  mesa-vulkan-drivers   19.3.3-1
ii  steam-devices 1.0.0.61-2
ii  xfce4-terminal [x-terminal-emulator]  0.8.9.1-1
ii  xterm [x-terminal-emulator]   353-1

Versions of packages steam suggests:
pn  nvidia-driver-libs-i386  
ii  nvidia-vulkan-icd440.64-1

Versions of packages steam is related to:
ii  libc6   2.30-2
ii  libgl1  1.3.1-1
ii  libgl1-mesa-dri 19.3.3-1
ii  libglx-mesa0 [libglx-vendor]19.3.3-1
ii  libglx-nvidia0 [libglx-vendor]  440.64-1
ii  libxcb-dri3-0   1.13.1-5
ii  nvidia-driver   440.64-1
ii  nvidia-driver-libs  440.64-1
pn  nvidia-driver-libs-i386 

-- debconf information excluded

-- debsums errors found:
debsums: package steam is not installed