this post was submitted on 18 Jul 2023
11 points (100.0% liked)

Steam Deck

14848 readers
50 users here now

A place to discuss and support all things Steam Deck.

Replacement for r/steamdeck_linux.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.

These are not enforced, but they are encouraged.

Rules:

Link to our Matrix Space

founded 3 years ago
MODERATORS
Moxvallix@sopuli.xyz
codus@leby.dev
timi@lemmy.world
RolAIDS05@lemmy.world
Fubarberry@sopuli.xyz
RolAIDS05@sopuli.xyz
11
Steam deck discover Store not connecting to repo (feddit.de)
submitted 1 year ago by neeeeDanke@feddit.de to c/steamdeck@sopuli.xyz
6 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] neeeeDanke@feddit.de 2 points 1 year ago* (last edited 1 year ago) (1 children)

I am currently running 3.4.8 (Build 20230508.1). I only had the deck for a week or so so I haven't used other versions before.

Interestingly I have no other network issues

  1. It seems the beta channel is on the same version as I was on before.

  2. I only have one boot partition available

[–] socphoenix@midwest.social 2 points 1 year ago (2 children)

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.de 1 points 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 points 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