When i launch steam(flatpak version) from the desktop, the app keeps trying to launch shows a black window for a few seconds and then crashes and the process keeps repeating. The steam icon is present on the system tray so it is running in the background.

When i run it with flatpak run com.valvesotware.Steam steam starts and runs as normal but the logs show this error

Steam Runtime Launch Service: starting steam-runtime-launcher-service Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 239 steam-runtime-launcher-service[239]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam" Steam Runtime Launch Service: steam-runtime-launcher-service pid 239 exited Steam Runtime Launch Service: starting steam-runtime-launcher-service Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 372 steam-runtime-launcher-service[372]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam" Steam Runtime Launch Service: steam-runtime-launcher-service pid 372 exited Steam Runtime Launch Service: starting steam-runtime-launcher-service Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 377 steam-runtime-launcher-service[377]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam" Steam Runtime Launch Service: steam-runtime-launcher-service pid 377 exited Steam Runtime Launch Service: steam-runtime-launcher-service keeps crashing on startup, disabling

Is there anyway I can fix this so that steam launches correctly when it is launched from the desktop. I am on fedora kinoite with 5600h+5500m laptop

Edit : is this somehow related to the dbus access that it has¿?

  • meow@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    Enabling the Session Bus Access permission fixes it. The issue seems to just be that the permission is disabled by default.

    • Sentau@lemmy.one
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Thanks. I no longer get the error messages when running it from the terminal but I am getting the same issues i was getting earlier when I run it from the desktop