No issues, thanks a lot devs 
I’ve got this issue as well. Installed steam-native which works. However, anyone know whether I can now uninstalled steam-manjaro without losing my library? I guess it just removes the client without removing the library data, but am I right?
Keep Steam-manjaro this is what you want to use in theory.
I just enabled the Steam BETA for now.
The launcher of the package gnome-shell-extension-pop-shell stopped working for me after this update. The quickest way I found to fix it (although it might just be a very poor workaround) was to downgrade back to the previous version. This is the command I ran: sudo pacman -U /var/cache/pacman/pkg/gnome-shell-extension-pop-shell-1.2.0+119+gab87042-1-any.pkg.tar.zst
steam-manjaro is Steam. Remove that and Steam is no longer installed. steam-native is just a shortcut to run Steam without the runtime and needed dependencies.
Removing a package never removes user data, your library and settings will be intact.
Cheers, thanks! I suppose I will use steam-native for the time being.
I can’t reproduce that. Did you restart GNOME Shell, logout or reboot after updating?
something bad
with steam , black screen on start , no game , no account visible , game can be selected by icons in menu bar and launched ( proton is on version 6.3-6)
1 Like
Again…
1 Like
only steam-beta is ok ( steam-native failed still errors with browser)
1 Like
Everything seems good with this update. Kernel 5.14 is a bit faster than 5.13 (possibly a placebo). And I don’t have any problems with steam-runtime or steam-native. 
Edit:
Oh, I’m sorry. The second screenshot is steam-native. The steam-runtime browser turns out does broken with this update. But it’s OK. I always use steam-native anyway.
PS: No screenshot is a hoax, they said. (time GMT+7)
Screenshot2
Since the upgrade (including upgrading to linux514) I often get
[FAILED] Failed to start Light Display Manager
on boot. I then have to reboot via tty and maybe it works then. Yesterday it happened once and I thought it was a one time thing, but today I needen three tries to boot.
I did forget to do that. Silly me… It is working indeed.
I dug a little deeper. And I found a better solution. I am assuming that this all may have been the result of a virgl update. So I updated the Display Spice parameter (to support local spice only) and enabled OpenGL support using my chip set (i.e., an Intel processor). Then I changed back to using virtio and 3D acceleration. Everything is now working as it did before.
You should also remember to run updates on a TTY next time. When I started using Manjaro, I used to run updates on my KDE Plasma session, and I couldn’t get the logout screen to work when I attempted a reboot, so I ditched the desktop altogether when running updates ever since to avoid such problems.
1 Like
Sorry if OT, but what’s the difference between steam-manjaro and steam-native?
Thanks in advance.
As I mentioned above:
This is what it does, it opens steam with this script instead of directly starting the Steam execuable.
#!/bin/bash
export STEAM_RUNTIME=0
export STEAM_RUNTIME_HEAVY=0
# Workaround for dbus fatal termination related coredumps (SIGABRT)
# https://github.com/ValveSoftware/steam-for-linux/issues/4464
export DBUS_FATAL_WARNINGS=0
# Override some libraries as these are what games linked against.
export LD_LIBRARY_PATH="/usr/lib/steam:/usr/lib32/steam${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
exec /usr/lib/steam/steam "$@"
And it adds /usr/lib32/steam and /usr/lib/steam libraries to be used with the startup script.
1 Like