I’m getting a weird issue with steam on my desktop running endeavourOS with qtile, where steam starts and then immediately closes. I’ve been trying to figure out why this happens, but all of the solutions I could find from googling errors have said to uninstall xdg-desktop-portal or flatpak, but neither of those things worked for me, nor did running steam with the -no-cef-sandbox or -vgui. It’s also worth noting that steam boots perfectly fine on my laptop (endeavourOS + KDE).

Here’s the result from running steam:

steam.sh[60179]: Running Steam on endeavouros rolling 64-bit
steam.sh[60179]: STEAM_RUNTIME is enabled automatically
setup.sh[60253]: Steam runtime environment up-to-date!
steam.sh[60179]: Steam client's requirements are satisfied
[2023-07-09 12:18:01] Startup - updater built Jun 21 2023 21:17:38
[2023-07-09 12:18:01] Startup - Steam Client launched with: '/home/[username]/.local/share/Steam/ubuntu12_32/steam'
07/09 12:18:01 Init: Installing breakpad exception handler for appid(steam)/version(1687386907)/tid(60314)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2023-07-09 12:18:01] Loading cached metrics from disk (/home/[username]/.local/share/Steam/package/steam_client_metrics.bin)
[2023-07-09 12:18:01] Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults
[2023-07-09 12:18:01] Using the following download hosts for Public, Realm steamglobal
[2023-07-09 12:18:01] 1. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2023-07-09 12:18:01] Checking for update on startup
[2023-07-09 12:18:01] Checking for available updates...
[2023-07-09 12:18:01] Downloading manifest: http://media.steampowered.com/client/steam_client_ubuntu12
[2023-07-09 12:18:01] Manifest download: send request
[2023-07-09 12:18:02] Manifest download: waiting for download to finish
[2023-07-09 12:18:02] Manifest download: finished
[2023-07-09 12:18:02] Download skipped: /client/steam_client_ubuntu12 version 1687386907, installed version 1687386907, existing pending version 0
[2023-07-09 12:18:02] Nothing to do
[2023-07-09 12:18:02] Verifying installation...
[2023-07-09 12:18:02] Performing checksum verification of executable files
[2023-07-09 12:18:02] Verification complete

(process:60314): GLib-GObject-CRITICAL **: 12:18:02.475: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:60314): GLib-GObject-CRITICAL **: 12:18:02.475: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xec817db0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xec816500
GetWin32Stats: display was not open yet, good
Loaded SDL version 3.0.0-1782-g214d5daa3

(steam:60314): Gtk-WARNING **: 12:18:02.549: Unable to locate theme engine in module_path: "adwaita",

(steam:60314): Gtk-WARNING **: 12:18:02.549: Unable to locate theme engine in module_path: "adwaita",
/usr/share/themes/Arc-Dark/gtk-2.0/main.rc:1090: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Arc-Dark/gtk-2.0/apps.rc:91: error: unexpected identifier 'direction', expected character '}'
GetWin32Stats: display was not open yet, good
steamwebhelper.sh[60356]: Runtime for steamwebhelper: defaulting to /home/[username]/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[60356]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
Failed to init SteamVR because it isn't installed
Assertion 'device' failed at src/libsystemd/sd-device/device-private.c:103, function device_get_tags_generation(). Aborting.
crash_20230709121803_27.dmp[60547]: Uploading dump (out-of-process)
/tmp/dumps/crash_20230709121803_27.dmp
/home/[username]/.local/share/Steam/steam.sh: line 798: 60314 Aborted                 (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"
crash_20230709121803_27.dmp[60547]: Finished uploading minidump (out-of-process): success = yes
crash_20230709121803_27.dmp[60547]: response: CrashID=bp-84664b98-84d4-4b31-8857-26fff2230709
crash_20230709121803_27.dmp[60547]: file ''/tmp/dumps/crash_20230709121803_27.dmp'', upload yes: ''CrashID=bp-84664b98-84d4-4b31-8857-26fff2230709''

Edit: Also not sure if there’s a better community to ask this in since this one seems to be mostly about news, I can ask elsewhere if this is the wrong community for debugging/help questions

Edit 2: I realized I didn’t specify, but my system has a Ryzen 7 5700x/RX 5700XT so it isn’t an issue with Nvidia drivers

Edit 3: Not sure why I put “Arch” in the title, just realized the mistake and fixed it. I’m on EndeavourOS, which is arch-based but obviously not the same thing.

Final Edit: Thanks for the help everyone! Installing the lib32-libnm package fixed it for me. If that doesn’t work for others, maybe try installing the flatpak version of steam, since that version was launching for me also

  • Digester@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    How exactly did you install steam? Maybe delete the files and try installing it from a difference source.

    • Zangoose@lemmy.oneOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      I just installed it through pacman. I’m contemplating moving over to the flatpak version but I really don’t want to have to redownload all of my games

      • entropicdrift@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        You don’t have to redownload all your games. I just switched to the flatpak this past month, here’s what I did:

        Leave steam installed natively, install the flatpak alongside it, using flatpak steam, open the root of the library folder (should be steamapps), then find the corresponding folder from the native install and recursively hardlink all the files from the native install’s steamapps folder to the flatpak’s steamapps folder. Quit steam and reopen and all your games should be detected.

        It’ll need to “update” basically all of them for at least a second to verify the files and it might need to re-process Vulkan shaders, but that’s it.

        • Zangoose@lemmy.oneOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          how do I hardlink files? I’ve been using linux for a few years but I’ve never really used links before for files. This seems to be the best strategy because everything else hasn’t worked so far

          • entropicdrift@lemmy.sdf.org
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            1 year ago

            cp -lr <src> <target>

            That command should do it

            cp is the copy paste CLI tool. -l (it’s a lowercase L) flag tells it to make a hard link instead of a second copy of the data itself on the disk. The -r flag tells it to recurse, so “do this copy operation on everything in every folder under the top level directory I hand you to copy”

            • Zangoose@lemmy.oneOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              1 year ago

              Thanks for this! I ended up fixing the local steam install (ended up being a network manager problem with steam) but I’ll keep this in mind because I’ll probably want to switch to the flatpak version in the future anyway

              • entropicdrift@lemmy.sdf.org
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                Eh, honestly, since Steam updates itself you’re probably fine without the flatpak unless you have a reason to need it.

  • shadow@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Just install the lib32-libnm package. The one Steam is supplying is outdated with the new libgudev 238-1, by installing your own lib32-libnm your system will use that over Steams one and it should launch fine.

  • iamak@infosec.pub
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    1 year ago

    Nvidia GPU I’m assuming? Make sure nvidia (or nvidia-dkms), nvidia-utils and lib32-nvidia-utils have the same version and are up to date. This issue is listed in the Arch Wiki see if it’s helpful for you.

      • Digester@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Try running these commands

        mv ~/.local/share/Steam ~/SteamBackup

        mv ~/.steam ~/SteamBackup steam

        Then launch steam by disabling direct write

        steam -no-dwrite

          • Digester@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            Did you check if you have any conflicting libraries?

            You can also try replacing the steam folder with the one on your laptop. If that doesn’t work it’s a problem with the OS on your PC. If you can’t trace it back you might want to reinstall the distro. Just back up your files

            • Zangoose@lemmy.oneOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Apparently it was a problem with their network manager library, installing lib32-libnm ended up fixing it for me. (I’m assuming my laptop already had that installed as a dependency for something else or as part of the default KDE install)

      • iamak@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Oh. Can you launch games using the commandline? I don’t know how this works but I was having same issue with Nvidia and I launched a game with command line and it started working. It probably was a coincidence but it’s worth trying I guess.

        • Zangoose@lemmy.oneOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Looks like no because it’s still trying to open steam when I try to run the games.

          • iamak@infosec.pub
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            Oh nvm then. Was worth a try. Anyways I see you solved it. Happy gaming! :)

  • Raphael@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    5
    ·
    edit-2
    1 year ago

    Glad you enjoyed the arch experience! How fun was it to waste time debugging this?

    • Zangoose@lemmy.oneOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      At least it got fixed eventually this time. Ricing tiling window managers for random seemingly small things is hard 😭