Steam doesn't start when launching it from app menu, but works with run command about com.valvesoftware.steam HOT 15 OPEN

The issue of Steam not launching from the desktop launcher on dual-GPU systems (which seems to be the original issue here) was supposed to have been solved in the Flatpak package, but it seems part of it was accidentally reverted. I've just sent in #1172 to reinstate the fix to that.

from com.valvesoftware.steam.

I had the same (or at least similar?) issue with an AMD CPU with internal graphics + an AMD graphics card that lead me to this post. The current workaround seems to be to set PrefersNonDefaultGPU to false in any of the desktop files that Flatpak creates and then update the desktop file database cache, either by logging out and back in or by running update-desktop-database. I still get the Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam" error when launching Steam from the terminal but I'm not sure if/how they're related. At least Steam opens without immediately closing again. (I'm on Fedora 38 Silverblue.)

from com.valvesoftware.steam.

Hey, I also have this "Unable to acquire bus name" error since I got the last Steam client update from September 11th, as I reported here: #1166.

I also use Debian 12 (with Gnome).

But for me, Steam launches just fine from the app menu and I only see this error in Gnome logs.

from com.valvesoftware.steam.

Hey, I also have this "Unable to acquire bus name" error since I got the last Steam client update from September 11th, as I reported here: #1166.

I also use Debian 12 (with Gnome).

But for me, Steam launches just fine from the app menu and I only see this error in Gnome logs.

I instead use KDE Plasma. Might have to add that to the issue

from com.valvesoftware.steam.

same errors with straight openbox (or using lxdm); though i cannot get the launcher to load a 2nd time, hangs at "loading user data" (first time i could only see friends list if and only if i alt-tabbed to it, main steam window was invisible 100% except for hover-over menus sometimes showed some text)

from com.valvesoftware.steam.

same errors with straight openbox (or using lxdm); though i cannot get the launcher to load a 2nd time, hangs at "loading user data" (first time i could only see friends list if and only if i alt-tabbed to it, main steam window was invisible 100% except for hover-over menus sometimes showed some text)

I was also having this same issue with virtualbox.

entering flatpak run com.valvesoftware.Steam -cef-disable-gpu into the terminal seem to fix the issue for me.

also steam -cef-disable-gpu worked for the non flatpak version of steam for me.

from com.valvesoftware.steam.

Same problem with KDE, but in fedora.
Also I am not using Nvidia gpu, and no driver error pops out.

from com.valvesoftware.steam.

Same here with KDE on kUbuntu
Using a Intel iGPU, on a Asus UX410U
Though I'm getting the issue regardless of using the shortcut or command line.
Steam UI opens for a second then closes

Desktop session is Wayland

from com.valvesoftware.steam.

I confirm this when clicking Steam icon from KDE menu, I get the error messages in journalctl

The output of $ journalctl --no-pager -p 3 -b --output=cat

E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"
E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"
E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"

I do not use Nvidia, but using AMD GPU and mesa.

Run the command line in the terminal:
$ /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/steam --file-forwarding com.valvesoftware.Steam @@u %U @@

The output:

...
steamwebhelper.sh[155]: Runtime for steamwebhelper: defaulting to /home/zesko/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[155]: Running under Flatpak, disabling sandbox
steamwebhelper.sh[155]: CEF sandbox already disabled
CAppInfoCacheReadFromDiskThread took 30 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 317
steam-runtime-launcher-service[317]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"
Steam Runtime Launch Service: steam-runtime-launcher-service pid 317 exited
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 357
steam-runtime-launcher-service[357]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"
Steam Runtime Launch Service: steam-runtime-launcher-service pid 357 exited
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 361
steam-runtime-launcher-service[361]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"
Steam Runtime Launch Service: steam-runtime-launcher-service pid 361 exited
Steam Runtime Launch Service: steam-runtime-launcher-service keeps crashing on startup, disabling
...

from com.valvesoftware.steam.

The output of $ journalctl --no-pager -p 3 -b --output=cat

E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"
E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"
E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"

Run $ flatpak run --socket=session-bus com.valvesoftware.Steam to fix this issue. The error is gone.

It looks like Steam needs to access a session-bus. I am not sure, why Steam needs the session-bus.

If you need to manage permission of Flatpak-applications, install flatpak-kcm as GUI for KDE on any Arch based distros. It is nice for beginner.

from com.valvesoftware.steam.

The proper fix to the warning here is to add com.steampowered.PressureVessel.LaunchAlongsideSteam.* to its own name

from com.valvesoftware.steam.

The proper fix to the warning here is to add com.steampowered.PressureVessel.LaunchAlongsideSteam.* to its own name

$ flatpak run --own-name="com.steampowered.PressureVessel.LaunchAlongsideSteam.*" com.valvesoftware.Steam

or

flatpak-kcm -> Steam -> Session bus policy -> Add new -> com.steampowered.PressureVessel.LaunchAlongsideSteam.* and own

Thanks!

from com.valvesoftware.steam.

The proper fix to the warning here is to add com.steampowered.PressureVessel.LaunchAlongsideSteam.* to its own name

$ flatpak run --own-name="com.steampowered.PressureVessel.LaunchAlongsideSteam.*" com.valvesoftware.Steam

or

flatpak-kcm -> Steam -> Session bus policy -> Add new -> com.steampowered.PressureVessel.LaunchAlongsideSteam.* and own

Thanks!

Aside from these, you can also use flatseal.

To fix this upstream, it has to be added on the finish-args in the flatpak manifest (.yml)

from com.valvesoftware.steam.

The E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam" errors are likely not related to the Steam client itself not starting up. I see them as well and it doesn't stop the client from functioning.

However, if we're already off-topic:

The proper fix to the warning here is to add com.steampowered.PressureVessel.LaunchAlongsideSteam.* to its own name

@smcv, is the Steam Flatpak expected to own a D-Bus namespace under com.steampowered.PressureVessel?

Edit: this would be the proper issue to discuss this: #1166

from com.valvesoftware.steam.

@jntesteves Thank you for the fix. The issue is gone for me in the re-released (?) 1.0.0.78.

from com.valvesoftware.steam.