Open luckyboy66666666 opened 1 year ago
Same issue here, except with Gnome 44.1 running on Wayland.
It does appear that the core issue is spawning the Steam window as all of the background processes continue to work. For example, clicking on anything on the system widget does show in the logs, along with other usual messages.
<--- Freeze of splash screen occurs here --->
(steam:2094358): GLib-GObject-CRITICAL **: 15:57:26.991: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(steam:2094358): GLib-GObject-CRITICAL **: 15:57:26.991: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
ExecuteSteamURL: "steam://open/steam://open/games"
ExecuteSteamURL: "steam://open/steam://open/friends"
[2023-06-18 15:59:24] Background update loop checking for update. . .
[2023-06-18 15:59:24] Checking for available updates...
[2023-06-18 15:59:24] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_publicbeta_ubuntu12?t=248595830
[2023-06-18 15:59:24] Manifest download: send request
[2023-06-18 15:59:24] Manifest download: waiting for download to finish
[2023-06-18 15:59:24] Manifest download: finished
[2023-06-18 15:59:24] Download skipped by HTTP 304 Not Modified
[2023-06-18 15:59:24] Nothing to do
ExecuteSteamURL: "steam://open/steam://url/CommunityHome"
ExecuteSteamURL: "steam://open/steam://open/bigpicture"
ExecuteSteamURL: "steam://open/bigpicture"
The steamwebhelper.log
does point to an issue (Invalid browser dimensions: 0 x 0
):
[0618/154710.090373:INFO:CONSOLE(1)] "WebSocket connection to 'ws://127.0.0.1:41881/transportsocket/' failed: Error during WebSocket handshake: Unexpected response code: 403", source: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=002fe41b9<snip> (1)
[0618/154710.090797:INFO:CONSOLE(1)] "%cWebUITransport%c: color: white; background: rgb(0,0,0); padding: 0 1ch color: transparent; margin-right: -1ch WebSocked error: [object Event]", source: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=002fe41b9<snip> (1)
[0618/154710.091894:INFO:CONSOLE(1)] "%cWebUITransport%c: color: white; background: rgb(0,0,0); padding: 0 1ch color: transparent; margin-right: -1ch MakeReady: failed to connect to SteamUI", source: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=002fe41b9<snip>(1)
[0618/154710.091927:INFO:CONSOLE(1)] "Failed to initialize webui transport", source: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=002fe41b9<snip> (1)
Invalid browser dimensions: 0 x 0
src/webhelper/html_chrome.cpp (3269) : CefCurrentlyOn( TID_UI )
Otherwise, nothing really obvious shows up.
Tested with the stable release and the latest beta (June 17th re-release) and with the latest Nvidia drivers (535) and the version previous (530). The same tests all under X11 work fine in all combinations. This is all on a Ubuntu 23.04 system.
steam with -bigpicture seems to work for me even when normal one is broken.
Launching steam with -vgui runs with old UI. But the friends tab seems to be broken and shows as disconnected even though it isn't.
Thank you, running with -vgui fixed it for me, since I don't have any friends. I use Ubuntu with an rx7900xtx and other good specs. I don't know how to get the steam logs, but I'll link the text file from when I ran it in the command line. steamBug.txt
Running with -vgui works to start Steam, however, Dota 2 graphical performance is impacted drastically. For some reason FPS drops from ~150 down to less than 10 and it is unplayable. Very odd!
I notice in other issues removing xdg-desktop-portal-gnome
is a common suggestion so just making a mention here that it has no effect.
This also persists with today's beta client patch applied.
For me, -vgui just had Steam hang on logging me in, although that was probably just a weird networking fluke. Steam has no trouble logging me in on the new UI.
On Tue, Jun 20, 2023, 02:40 Edward Savage @.***> wrote:
Running with -vgui works to start Steam, however, Dota 2 graphical performance is impacted drastically. For some reason FPS drops from ~150 down to less than 10 and it is unplayable. Very odd!
I notice in other issues removing xdg-desktop-portal-gnome is a common suggestion so just making a mention here that it has no effect.
This also persists with today's beta client patch applied.
— Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/steam-for-linux/issues/9658#issuecomment-1598360196, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHFQFTEEGQGBJXWKW6P6HLXMFOYHANCNFSM6AAAAAAZKTMRUM . You are receiving this because you authored the thread.Message ID: @.***>
I was getting the same error, with -vgui
worked but friends tab didn't worked.
After reseting steam with steam --reset
it worked.
I can confirm this issue is happening on archlinux. steam --reset
did nothing but steam -vgui
works just fine aside from the friends network being broken and appearing offline. Running on NVIDIA graphics.
Seems to be related to #9634. I was on driver 535.54.03-1 and I saw the same invalid opcode
errors from there, in dmesg
. I downgraded the NVIDIA Drivers to 530.41.03 and the issue is no longer reproducible.
No opcode errors in dmesg in my case nor does downgrading the driver help.
Retested with all the fixes in the last two days betas, no dice, even after --reset
.
I'm getting the same after picking up the latest package from the Manjaro repositories. Full details follow:
I've been trying to get Steam running on my new Manjaro Cinnamon build with very mixed results.
I managed to get it running once and tested some games then on reboot the Steam Client would not load, either in (Native) or (Runtime) variants.
I tried uninstalling and re-installing the steam packages to no avail.
After looking for help online I first did steam --reset
- This didn't help, so I went to the next step and renamed my ~/,steam' and '~/.local/share/Steam
directories.
I then ran it again and this time it loaded up, so I installed a few games again and tested them through. Performance was lacklustre, so I tweaked the CPU power performance and rebooted. 1 game was looking better but another was still not great so I tried switching a proton version and it crashed, so I went for a reboot.
On reboot, once more the Steam client would not start.
I ran steam --reset
and it then started... once. After exiting and trying to start normally it just stopped again, now it's not starting with steam --reset
again and I seem to be back at the beginning.
When I run steam my output looks like this (on steam --reset
)...
/home/keith/.local/share/Steam/steam.sh: line 487: no match: ssfn*
steam.sh[13348]: Running Steam on manjarolinux 23.0.0 64-bit
steam.sh[13348]: STEAM_RUNTIME is enabled automatically
setup.sh[13425]: Steam runtime environment up-to-date!
steam.sh[13348]: Steam client's requirements are satisfied
[2023-06-29 22:28:54] Startup - updater built Jun 21 2023 21:17:38
[2023-06-29 22:28:54] Startup - Steam Client launched with: '/home/keith/.local/share/Steam/ubuntu12_32/steam' '--reset'
06/29 22:28:54 Init: Installing breakpad exception handler for appid(steam)/version(1687386907)/tid(13493)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2023-06-29 22:28:54] Loading cached metrics from disk (/home/keith/.local/share/Steam/package/steam_client_metrics.bin)
[2023-06-29 22:28:54] Using the following download hosts for Public, Realm steamglobal
[2023-06-29 22:28:54] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2023-06-29 22:28:54] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2023-06-29 22:28:54] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2023-06-29 22:28:54] Checking for update on startup
[2023-06-29 22:28:54] Checking for available updates...
[2023-06-29 22:28:54] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_ubuntu12
[2023-06-29 22:28:54] Manifest download: send request
[2023-06-29 22:28:54] Manifest download: waiting for download to finish
[2023-06-29 22:28:54] Manifest download: finished
[2023-06-29 22:28:54] Download skipped: /steam_client_ubuntu12 version 1687386907, installed version 1687386907, existing pending version 0
[2023-06-29 22:28:54] Nothing to do
[2023-06-29 22:28:54] Verifying installation...
[2023-06-29 22:28:54] Performing checksum verification of executable files
[2023-06-29 22:28:55] Verification complete
(process:13493): GLib-GObject-CRITICAL **: 22:28:55.064: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(process:13493): GLib-GObject-CRITICAL **: 22:28:55.064: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe4d31db0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe4d30500
GetWin32Stats: display was not open yet, good
Loaded SDL version 3.0.0-1782-g214d5daa3
/usr/share/themes/Adapta-Nokto-Maia/gtk-2.0/common-dark.rc:1425: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Adapta-Nokto-Maia/gtk-2.0/3rd-party-dark.rc:475: error: invalid string constant "toolbar", expected valid string constant
GetWin32Stats: display was not open yet, good
steamwebhelper.sh[13562]: Runtime for steamwebhelper: defaulting to /home/keith/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[13562]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
CAppInfoCacheReadFromDiskThread took 11 milliseconds to initialize
src/steamUI/steamuisharedjscontroller.cpp (529) : Failed creating offscreen shared JS context
src/steamUI/steamuisharedjscontroller.cpp (529) : Failed creating offscreen shared JS context
src/steamUI/steamuisharedjscontroller.cpp (529) : Fatal assert; application exiting
src/steamUI/steamuisharedjscontroller.cpp (529) : Fatal assert; application exiting
06/29 22:29:26 Init: Installing breakpad exception handler for appid(steam)/version(1687386907)/tid(13493)
assert_20230629222927_31.dmp[13822]: Uploading dump (out-of-process)
/tmp/dumps/assert_20230629222927_31.dmp
_ExitOnFatalAssert
~ assert_20230629222927_31.dmp[13822]: Finished uploading minidump (out-of-process): success = yes ✔ 34s
assert_20230629222927_31.dmp[13822]: response: CrashID=bp-6cfdff34-5d73-4dc0-9367-9b0ea2230629
assert_20230629222927_31.dmp[13822]: file ''/tmp/dumps/assert_20230629222927_31.dmp'', upload yes: ''CrashID=bp-6cfdff34-5d73-4dc0-9367-9b0ea2230629''
Here's my INXI...
System:
Host: PLATINUM Kernel: 6.1.31-2-MANJARO arch: x86_64 bits: 64
Desktop: Cinnamon v: 5.6.8 Distro: Manjaro Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: PRIME Z690-P D4 v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1008
date: 01/13/2022
CPU:
Info: 6-core model: 12th Gen Intel Core i5-12600 bits: 64 type: MT MCP
cache: L2: 7.5 MiB
Speed (MHz): avg: 3075 min/max: 800/6100 cores: 1: 3300 2: 3300 3: 3300
4: 3300 5: 3300 6: 3300 7: 600 8: 3300 9: 3300 10: 3300 11: 3300 12: 3300
Graphics:
Device-1: Intel Alder Lake-S GT1 [UHD Graphics 770] driver: i915 v: kernel
Device-2: Microsoft LifeCam Studio
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: modesetting
dri: iris gpu: i915 resolution: 1: 5120x2880~60Hz 2: 5120x2880~30Hz
API: OpenGL v: 4.6 Mesa 23.0.4 renderer: Mesa Intel UHD Graphics 770
(ADL-S GT1)
Audio:
Device-1: Intel Alder Lake-S HD Audio driver: snd_hda_intel
Device-2: Microsoft LifeCam Studio
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB
API: ALSA v: k6.1.31-2-MANJARO status: kernel-api
Server-1: PulseAudio v: 16.1 status: active
Network:
Device-1: Realtek RTL8125 2.5GbE driver: r8169
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: 04:42:1a:e9:5a:c5
RAID:
Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
Drives:
Local Storage: total: 9.1 TiB used: 3.25 TiB (35.7%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 500GB
size: 465.76 GiB
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
ID-3: /dev/sda vendor: Western Digital model: WD40EZRZ-22GXCB0
size: 3.64 TiB
ID-4: /dev/sdb vendor: Western Digital model: WD40EZRZ-00GXCB0
size: 3.64 TiB
ID-5: /dev/sdc vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
Partition:
ID-1: / size: 465.47 GiB used: 207.9 GiB (44.7%) fs: btrfs
dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 598.8 MiB used: 2.4 MiB (0.4%) fs: vfat
dev: /dev/sdc1
ID-3: /home size: 465.47 GiB used: 207.9 GiB (44.7%) fs: btrfs
dev: /dev/nvme0n1p2
ID-4: /var/log size: 465.47 GiB used: 207.9 GiB (44.7%) fs: btrfs
dev: /dev/nvme0n1p2
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 47.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 378 Uptime: 24m Memory: available: 31.1 GiB
used: 5.29 GiB (17.0%) Shell: Zsh inxi: 3.3.27
I have just done a full uninstall of the Steam packages (steam linux-steam-integration steam-native-runtime), renamed my steam directroies again (as noted above), then a reboot and then ran pacman -S steam
with the following output...
resolving dependencies...
looking for conflicting packages...
Packages (2) game-devices-udev-0.21-1 steam-1.0.0.78-1
Total Installed Size: 3.85 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [################################################] 100%
(2/2) checking package integrity [################################################] 100%
(2/2) loading package files [################################################] 100%
(2/2) checking for file conflicts [################################################] 100%
(2/2) checking available disk space [################################################] 100%
:: Processing package changes...
(1/2) installing game-devices-udev [################################################] 100%
(2/2) installing steam [################################################] 100%
Optional dependencies for steam
steam-native-runtime: steam native runtime support
vulkan-driver: packaged vulkan driver [installed]
lib32-vulkan-driver: packaged vulkan driver (32 bit) [installed]
lib32-libappindicator-gtk2: added tray icon functionality [installed]
xdg-desktop-portal: required for steam-runtime-urlopen to open some URLs [installed]
:: Running post-transaction hooks...
(1/4) Reloading device manager configuration...
(2/4) Arming ConditionNeedsUpdate...
(3/4) Updating icon theme caches...
(4/4) Updating the desktop file MIME type cache...
On clicking the icon on the desktop various dialogs appeared, updating and installing parts of the Steam client and then everything went quiet again. Attempting to run from the command line is providing the same output as above. Not sure where to go from here - It feels like the package is broken.
This article on the Arch Wiki is potentially similar: https://bbs.archlinux.org/viewtopic.php?id=286683 And this: https://bbs.archlinux.org/viewtopic.php?id=286571 Which is linking to this very bug!
I've now tried all the parameter overrides posted here - none of them worked for me. The only thing I haven't tried is removing flatpak
which isn't really an option for me as I have essential Flatpak only software.
I found a workaround for this on my Manjaro Cinnamon install but it's ... weird.
The full details can be found on the Manjaro forum discussion here: https://forum.manjaro.org/t/problems-getting-steam-running/143276/19
THE (WEIRD) SOLUTION I can reproduce, with pretty much 95% plus surety that if I start up, with Steam set to run at startup (It will fail but silently) then after around 30 seconds I manually start docker desktop then close it all down steam will run like a charm.
I’ve tried disabling all the Startup applications (except Steam) and that made no difference at all. I have run some tests to see whether it’s actually the closing of docker desktop that’s helping or that it was started - I wondered whether DD is waking up something that Steam needs to run which it’s failing to kick itself.
This theory holds true.
It’s not closing Docker Desktop that gets Steam working, it’s actually running it.
I wonder if it’s not actually docker desktop that’s helping directly but a dependency that it kicks off. I wonder whether steam needs to use this or tries to kick it but it won’t respond? (I am purely guessing at this point) - The comments on the Arch Wiki in regard to flatpak may have a common source.
I’ve now set my Startup applications so that Docker Desktop starts after 15 seconds, with Steam starting at 2 (expecting it to fail that early on) - This seems to kick them both into touch and then, as long as you give it a minute or so, you can then reliable and rapidly start Steam!
It’s an odd workaround but I’ll report back over the next few days on it’s efficacy.
About this error: GLib-GObject-CRITICAL **: 15:57:26.991: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
seems that can be solved this way: https://stackoverflow.com/questions/75530422/g-object-unref-assertion-g-is-object-object-failed
I spent some more time playing with this today to look into the Docker Desktop report above.
While I couldn't replicate that result I did find that the main Steam window will partially spawn, very infrequently, if the frozen login screen is killed. In the second picture below you can see a menu with "Home", "Collections", and "Downloads". The other menus work, and if I guess where buttons are I can start games or open Chat, and move the window such that the menus open elsewhere.
If it's any help I grabbed xprop
and xwininfo
from this ghost window.
$ xwininfo
xwininfo: Window id: 0x1800006 "Steam"
Absolute upper-left X: 815
Absolute upper-left Y: 435
Relative upper-left X: 815
Relative upper-left Y: 435
Width: 1280
Height: 800
Depth: 32
Visual: 0x51b
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0x1800005 (not installed)
Bit Gravity State: ForgetGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsViewable
Override Redirect State: no
Corners: +815+435 -465+435 -465-205 +815-205
-geometry 1280x800+815+435
$ xprop
_NET_WM_STATE(ATOM) = _NET_WM_STATE_FOCUSED
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_DESKTOP(CARDINAL) = 0
_GTK_EDGE_CONSTRAINTS(CARDINAL) = 170
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW
XdndProxy(WINDOW): window id # 0x1200053
_NET_WM_ICON(CARDINAL) = Icon (128 x 128):
...snip ascii icon...
STEAM_GAME(CARDINAL) = 769
XdndAware(ATOM) = BITMAP
_NET_WM_NAME(UTF8_STRING) = "Steam"
WM_NAME(UTF-8) = "Steam"
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_NET_WM_PID(CARDINAL) = 78536
WM_LOCALE_NAME(STRING) = "en_AU.UTF-8"
WM_CLASS(STRING) = "steamwebhelper", "steam"
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
window id # of group leader: 0xd09ec3c8
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified location: 815, 435
program specified minimum size: 1010 by 600
WM_CLIENT_MACHINE(STRING) = ...snip...
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0
And for anyone else looking at env
as a possible source of this issue here's mine.
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu-wayland:/etc/xdg/xdg-ubuntu:/etc/xdg
DESKTOP_SESSION=ubuntu-wayland
XDG_SESSION_DESKTOP=ubuntu-wayland
XDG_SESSION_TYPE=wayland
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.8E3Q71
WAYLAND_DISPLAY=wayland-0
XDG_DATA_DIRS=/usr/share/ubuntu-wayland:/usr/share/ubuntu:/usr/share/gnome:/home/edward/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
GDMSESSION=ubuntu-wayland
WAYLAND_DISPLAY=wayland-0
GNOME_SETUP_DISPLAY=:2
DISPLAY=:1
GDK_BACKEND
and MUTTER_BACKEND
are unset.
All games started via the invisible library window cause buggy client warnings.
Jul 03 21:45:40 hostname gnome-shell[66772]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800211
Jul 03 21:45:40 hostname gnome-shell[66772]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800211
Jul 03 21:47:50 hostname gnome-shell[66772]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x280000e
Playing around with the ghost window can trigger a crash with this Mesa fault.
Jul 03 21:33:06 hostname kernel: llvmpipe-2[89525]: segfault at 7fe04bd50ffc ip 00007fe097c2e38a sp 00007fe0889fb240 error 4 likely on CPU 2 (core 2, socket 0)
Jul 03 21:33:06 hostname kernel: Code: fe dd c5 dd 72 e3 08 c4 c3 5d 4a e0 30 c5 d5 72 f7 02 c4 c2 5d 39 f0 c4 e2 4d 40 f1 c5 cd fe fd c4 41 2d 76 d2 c4 41 21 ef db <c4> 42 2d 90 1c 3a c4 c2 7d 58 3e c5 d5 fe ff c5 95 db ff c5 45 fe
$ glxinfo -B
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Mesa (0xffffffff)
Device: llvmpipe (LLVM 15.0.7, 256 bits) (0xffffffff)
Version: 23.0.2
Accelerated: no
Video memory: 15942MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 4.5
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 23.0.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.5 (Compatibility Profile) Mesa 23.0.2
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
Steam Diagnostics (Runtime Information)
Lots of unexpected initialisation failures with renderers like this one. Wayland might not have direct rendering but I'm imaging the Steam XWindow should have it. The libraries it says aren't available are on disk and I couldn't spot any stale copies from the named errors hanging around.
...
"x11/vdpau" : {
"messages" : [
"Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory",
"vdp_device_create_x11 (display, screen, &device, &vdp_get_proc_address) failed: 1"
],
"renderer" : null,
"version" : null,
"issues" : [
"cannot-draw"
],
"exit-status" : 1
},
...
Hopefully this points to something actually useful for debugging @kisak-valve. :crossed_fingers:
Hello @epssy, you're looking for #9752. In general, Steam falling back to llvmpipe means something is broken or missing from your system which is preventing you from using your GPU.
Yup, looks like a few of these Wayland tickets are all the same fallback case.
Though I'm a little confused why the rendering worked fine for months in the beta channel and only broke when the big UI refresh release went to the stable channel. All I did was update Steam on the day the patch came out and suddenly I couldn't use it on Wayland.
I'll step through the library imports tomorrow and see what file is broken or in the wrong place.
Though I'm a little confused why the rendering worked fine for months in the beta channel and only broke when the big UI refresh release went to the stable channel. All I did was update Steam on the day the patch came out and suddenly I couldn't use it on Wayland.
Exactly why I'm so weirded out by this bug since there was no indication of this prior.
Fixing GLX acceleration fixed Steam and games running within it. Thanks a bunch Kisak. :rocket:
I managed to get it to work by uninstalling steam, and then reinstalling without native-runtime. Assuming some libraries are conflicting, i didn't spend much time verifying the library. I double checked and broke it again by installing the native-runtime and the normal runtime stopped working again.
I didn't even have native-runtime installed before. Installing it and running Steam through that seems to have fixed my issue though, weirdly enough.
looks like -vgui is removed now even though issue is unresolved. very cool
looks like new steam ui has problems with my xorg configuration.
this (reduced) config uses igpu and dedicated gpu to run one screen each (i3 as wm)
Section "ServerFlags"
Option "AutoBindGPU" "off"
Option "AutoAddGPU" "off"
Option "DefaultServerLayout" "this0"
EndSection
Section "Screen"
Identifier "screen0"
Device "AMD Radeon RX 6700 XT"
EndSection
Section "Screen"
Identifier "screen1"
Device "cometlake"
EndSection
Section "ServerLayout"
Identifier "this0"
Screen 0 "screen0" 0 0
Screen 1 "screen1" LeftOf "screen0"
EndSection
Section "Device"
Identifier "AMD Radeon RX 6700 XT"
Driver "amdgpu"
BusID "PCI:3:0:0"
Option "VariableRefresh" "true"
EndSection
Section "Module"
Load "amdgpu"
EndSection
Section "Device"
Identifier "cometlake"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
Section "Module"
Load "intel"
EndSection
When I remove the igpu driven screen steam runs just fine. It also works when i run it under gamescope unmodified which is what made me think of my xorg config in the first place.
xorg --help
Command 'xorg' not found, did you mean:
command 'borg' from deb borgbackup (1.2.7-2)
command 'borg' from deb borgbackup-is-borgbackup2 (2.0.0b5-3)
command 'porg' from deb porg (2:0.10-1.2)
Try: sudo apt install <deb name>
altough man xorg
working due
Xorg --help
/usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server
because Xorg --init
or something like that generates config(but 20 years not necessity in Linux :-) which could then be via man xorg configured.
But now XWayland is Xorg ripped off and a lot of from Xorg is missing because Red Hat try to clean it for todays old issues.
So if Steam has problems it is maybe because Chromium and Steam stack upon that is not prepared well for Wayland and also WebGPU and a lot of programming is behind the curtain in Google for Chrome and Steam waits.
So maybe some xorg config do it, but reporting bugs and find what config do it is only part of equation for better XWayland and maybe game recompilation because new framework updates for games(like SDL) could bring native Wayland.
Your system information
Please describe your issue in as much detail as possible:
When I start my laptop, as usual, Steam starts up automatically. This time, it has the fancy new loading screen that I assume comes with the new UI update. But Steam never opens up into my library: the circle just perpetually spins. The Steam icon does appear in my system tray, but I can't open any recently-played games through it and trying to get to anything within the Steam runtime just results in a similar hang. Exiting Steam from the tray works, so when I do that and start Steam again, it checks for updates and seems to successfully log me into my account, but it freezes when trying to load whatever interface it's trying to load (I assume the store, but the hang happens when I try to open my library as well).
Steps for reproducing this issue: