I’m using Arch currently and the following issues have been present on every install of Steam I’ve had:

  • Controller inputs break constantly. If I use big picture mode, the games will be in some quasi state where it both detects my controller and doesn’t.
  • The menus take like 3 seconds to open.
  • The right click menu in the system tray does not work 30% of the time.
  • Worst of all, when I close a game, steam will not detect that it closes. Once this happens, no other page will load, no menus will open, and i have to killall steam -s SIGKILL, since no other signal works. It’s also survived SIGKILL multiple times. How?
  • In game, the shift+tab menu does not work; half the buttons are unresponsive and the game will crash upon closing shift+tab

The arch wiki had nothing on this.

Flatpak and native installs have the same problem, reinstallation does nothing, steam --reset does nothing.

These issues occur across multiple games with different engines.

It’s very strange since I have a very generic system and most people seem to have great experiences.

  • Zos_Kia@lemmynsfw.comEnglish
    4·
    4 hours ago

    One bug I’ve had for ages is that the client stops rendering so it looks like steam is frozen (heh) but if you just resize the window it unfreezes

  • BurgerBaron@piefed.socialEnglish
    1·
    4 hours ago

    I have almost none of those issues. CachyOS on two desktops. One is AMD CPU/Nvidia GPU, the other is Intel CPU/AMD GPU. Both KDE. I only use Steam native so far. 8bitdo Pro 2 controllers /w USB Wi-Fi 2.4Ghz dongles.

    Occasionally a game hangs, but only about often as I had it happen on Windows.

    The main problem I’m having is broken video playback on Store pages with their updated wide media player. Turns hardware acceleration on/off doesn’t fix it.

  • blaise@champserver.netEnglish
    4·
    12 hours ago

    Is steam the only program you’ve noticed having issues? If not then here’s a scary possibility to consider: Hardware Failure
    I recently had my power supply destroy my MB and SSD and there were signs that I ignored just before it all went down.
    If you still have your arch install usb available then boot from that and pick the memtest86 option in the boot menu to see if your ram has any faults.

    • Die4Ever@retrolemmy.comEnglish
      2·
      6 hours ago

      Power supply can cause memtest failures? How do you know if the issue is the RAM sticks, the mobo sockets, the CPU, or the PSU? Lol

  • 🇰 🌀 🇱 🇦 🇳 🇦 🇰 🇮 @pawb.socialEnglish
    281·
    1 day ago

    I have all these problems on occasion on Windows, too. They’re just problems with Big Picture mode.

    The first one tho, with the controller wonkiness, is usually caused by leaving Steam Input enabled in a game that 100% natively supports your controller. If the game shows a totally filled in version of your controller, you should disable Steam Input and just let the game handle it.

  • MrQuallzin@lemmy.worldEnglish
    1·
    13 hours ago

    For the controller issues, run games with Proton 9.x. As far as I know controllers don’t work right with Proton 10.x

  • treep@lemmy.worldEnglish
    2·
    15 hours ago

    One thing I have with controllers is, that when I do the old -Syu and there are OS level packages in there, steam won’t detect any controller until I do a reboot, even if the OS itself detects it.

    Other than that there are some games that have full controller support but still only work with steam input. It’s trial and error with every game.

    Also in i3 steam doesn’t like being tiled and wants to be floated (does not react to mouse inputs otherwise), but in hyprland it doesn’t care either way. If you’re using i3 or something similar, maybe this is related?

  • De Lancre@lemmy.worldEnglish
    1·
    16 hours ago

    I had all those issues on arch for a while, but recent (this week) update indeed seems to bork something even more. Not sure if it was steam update or arch os update, but currently steam window have 50/50 chance to become laggy af and unresponsive. Basically making it unusable. Closing to tray and opening again can fix it with same 50/50 chance.

    Have no clue how to fix it. Check their github, maybe someone already reported a bug.

  • JetpackJackson@feddit.orgEnglish
    53·
    22 hours ago

    So far im not having any issues with steam games (1 day old cachyos install on new (for me) pc, native steam). I know that’s not really that helpful but I hope that you get it figured out

  • cannedtuna@lemmy.worldEnglish
    3·
    1 day ago

    Yo me too!

    I close a game and Steam thinks it’s still open. Or I close Steam window and can’t reopen it and have to send a Kill signal and relaunch. Using the packaged version with CachyOS, which I believe is from Aur.

    Issue with Native I guess since if you launch just Steam, it launches Steam (Native)

    For reference I’m using KDE

    • Xylight@lemdro.idOPEnglish
      2·
      1 day ago

      Flatpak and native installs have the same problem

      I am currently using a Flatpak

      • just_another_person@lemmy.worldEnglish
        25·
        22 hours ago

        Thanks for the quote, but 6-7 and you don’t specify.

        You’re having an issue with the game engine. Try running it outside of Steam via Heroic or straight Wine.

        Also try it in Desktop Mode and see if it works there to widdoe it down.