I’ve had a few issues with the discover store only working sporadicly in desktop mode amd when looking it up found ne good solutions that don’t require a system restart or work reliably.

The error I had was something along the lines of a lost connection due to a refused TSL-Handshake these are the errors I get trying to refresh the available updates for example:

I press update All and get:

no metadata URIs for vendor-directory

I press it again:

the application […]/x86_64/stable requires the runtime org.kde.Platform/x86_64/6.4 which was not found

and again:

aborted due to failure (While pulling runtime/org.kde.Platform.Locale/x86_64/6.4 from remote flathub: Peer failed to perform TLS handshake: Error recieving data: Connection reset by peer)

I would love it if anyone can help me with this as I would like to be able to reliably update my packages (and install new ones which often jeilds the same errors)

I have tried installing over the terminal, which results in the same errors. I have tried it on different Networks. I have restartes flatpak-sytem-helper. service as well as wpa_suppclient.service I have tried flatpack repair. Restarts of the whole system work occasionally but not reliably.

  • socphoenix@midwest.social
    2·
    1 year ago

    Build 20230508.1 is out of date. Under settings->system the top two buttons should be “check for updates” and then under the beta participation header “System Update Channel”. I’m on the same build and system update channel shows “stable”, with an upgrade available when I checked.

    If yours doesn’t show one available, the system update channel has 3 options:

    1. Stable
    2. Beta
    3. Preview

    Pick the one above what it’s set to now to try and force an update. As a note, preview is likely to be unstable. Even if it fixes it I’d recommend going back to one of the other two options, it’ll “update” again and reboot after that.

    My best guess is that flathub/its ssl dependency may have somehow been corrupted and forcing it to reinstall the app through updates should fix it.

    • neeeeDanke@feddit.deOP
      1·
      1 year ago

      Thanks, I didn’t know what you ment by forcing an update before, but that seems to have worked :D

    • socphoenix@midwest.social
      1·
      1 year ago

      Correction I guess update didn’t change the build number… thanks steam for making sense. The bottom half of what I wrote should still help. I’d try switching to prieview (or stable assuming you’re on beta) and forcing an is update that way then switching back to what you want. SteamOS has gotten a lot better since day 1 but for the occasional issue this has almost always seemed to work for me