ValveSoftware / steam-runtime

A runtime environment for Steam applications
Other
1.17k stars 86 forks source link

steamwebhelper p-v-adverb: error while loading shared libraries: libdl.so.2 #670

Closed vochant closed 1 month ago

vochant commented 1 month ago

System information

Details

I installed steam from apt (and i got a same error when using the package from .deb file). When i try to run it, i will get a dialog shows "steamwebhelper is not responding." I tried to disable GPU Acceleration or disable Browser Sandboxing, but the problem still exists.

I confirm that there are no issues with system runtime libraries, whether it is 32-bit or 64 bit.

steamwebhelper.log shows that pressure-vessel-adverb cannot find libdl.so.2, but both locate and whereis can find it, and ldd shows nothing was not found.

Steps for reproducing this issue:

I don't know why it will happen on my computer, maybe you cannot reproduce it on your computer.

  1. Install Steam Linux
  2. Run it.
kisak-valve commented 1 month ago

Hello @vochant, since this is an issue with pressure vessel setting up the Steam Linux Runtime - Sniper container environment for Steam's web component to run inside, that makes your issue more of a Pressure Vessel issue for a runtime dev to ponder than a general Steam client issue, so I've transferred this issue report to the steam-runtime issue tracker.

Please give https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md#essential-information a read and share a steamwebhelper.log from trying to start Steam with STEAM_LINUX_RUNTIME_LOG=1.

vochant commented 1 month ago

webhelper.txt

vochant commented 1 month ago

@kisak-valve Do you need more informations like dump file?

smcv commented 1 month ago

webhelper.txt

We'll probably need to see steamwebhelper.log, not webhelper.txt (but it's safest if you just attach both).

with STEAM_LINUX_RUNTIME_LOG=1

Instead of STEAM_LINUX_RUNTIME_LOG, please use STEAM_LINUX_RUNTIME_VERBOSE=1.

smcv commented 1 month ago
  • Distribution: Ubuntu 22.04LTS

I cannot reproduce this issue on an Ubuntu 22.04 test system.

(Updated from NOI Linux)

Switching between different distros in-place is not usually something that can be supported. The process of upgrading from NOI Linux to Ubuntu 22.04 might have left your system in an unusual state.

To be able to make any progress on this issue report, we will need to see detailed logs with STEAM_LINUX_RUNTIME_VERBOSE=1 as requested in my previous comment. Please don't use STEAM_LINUX_RUNTIME_LOG=1 in this case: if you do that, the log will appear in a different location which is harder to find.

The filename of the log that we need to see has changed in recent Steam versions, so it is safest to attach all of the logs from ~/.steam/steam/logs again (for example with the command from the steam-for-linux issue template, tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs).

smcv commented 1 month ago

@kisak-valve, is there a "needs info" label that you can attach to issues that are waiting for more info from the issue reporter?

vochant commented 1 month ago

Sorry, i cannot provide any more information because i reinstalled my system, and the problem hasn't happened again. About NOI Linux, strictly speaking, this is not an independent distribution, but simply an adjustment to Ubuntu of some software.

There is a backup before reinstalling the system: https://pan.huang1111.cn/s/K28KsY

The problem may arise during the system upgrade process, where an unexpected shutdown resulted in the coexistence of old and new versions of files, but the problem only occurred on a very small number of applications. I reinstalled NOI Linux and updated to Ubuntu 22.04LTS, but this problem hasn't happened again.

This is likely not a bug.