decky-loader icon indicating copy to clipboard operation
decky-loader copied to clipboard

[BUG] Decky not showing

Open Ayorin opened this issue 1 year ago • 6 comments

Please confirm

  • [X] I have searched existing issues
  • [X] This issue is not a duplicate of an existing one
  • [X] I have checked the common issues section in the readme file
  • [X] I have attached logs to this bug report (failure to include logs will mean your issue may not be responded to).

Bug Report Description

Decky icon disappeared after being installed, i tried to unistall and reinstall but nothing change.Both stable and prerelease doesn't seems to work.

Expected Behaviour

Working

SteamOS version

SteamOS 3.5.7 Stable

Selected Update Channel

Stable

Have you modified the read-only filesystem at any point?

No response

Backend Logs

deckylog.txt

Frontend Logs

cef_log.txt cef_log.previous.txt

Ayorin avatar Jun 17 '24 11:06 Ayorin

Reading your deckylog.txt file, there's an error: '/json did not return 200. 404 page not found\n'. This likely means it found something on port 8080, but it wasn't steam. Probably caused by you installing something recently that runs on port 8080, like syncthing. Just change the port from 8080 for syncthing or whatever you installed to anything else and it should be fine

(this problem is listed in the common issues of the readme by the way)

PartyWumpus avatar Jun 17 '24 12:06 PartyWumpus

Reading your deckylog.txt file, there's an error: '/json did not return 200. 404 page not found\n'. This likely means it found something on port 8080, but it wasn't steam. Probably caused by you installing something recently that runs on port 8080, like syncthing. Just change the port from 8080 for syncthing or whatever you installed to anything else and it should be fine

(this problem is listed in the common issues of the readme by the way)

Do you think it would be possible to find a way for the backend to use another port if it's in use?

I feel like that could be a very common issue since many users have other services running on their Deck I imagine

bricefriha avatar Jun 25 '24 09:06 bricefriha

Do you think it would be possible to find a way for the backend to use another port if it's in use?

Decky didn't choose 8080, it's the port valve uses for CEF debugging, which we connect to. It is possible to change this port, I think, but it would require modifying the steam startup script. Decky generally tries to avoid system modification, so I'm not sure if we should. Probably better to test for it in the installer.

(Decky uses 1337 for itself, which could be changed but I don't think I've actually seen a collision with that yet)

PartyWumpus avatar Jun 25 '24 10:06 PartyWumpus

Reading your deckylog.txt file, there's an error: '/json did not return 200. 404 page not found\n'. This likely means it found something on port 8080, but it wasn't steam. Probably caused by you installing something recently that runs on port 8080, like syncthing. Just change the port from 8080 for syncthing or whatever you installed to anything else and it should be fine

(this problem is listed in the common issues of the readme by the way)

In my case, it looks like steamwebhelper is listening on 8080. Is there any way to change that? My error is that Decky shows up on boot, but every plugin shows "Something went wrong while displaying this content" and then Decky goes away until another reboot happens.

I also noticed that every plugin has this error when I reinstall them: "plugin_exports.default is not a function". I'm on stable channels all the way around.

ninjanerdbgm avatar Jul 18 '24 17:07 ninjanerdbgm

Steamwebhelper is what is supposed to be on port 8080, your issue is unrelated to this one.

PartyWumpus avatar Jul 18 '24 18:07 PartyWumpus

Do you think it would be possible to find a way for the backend to use another port if it's in use?

Decky didn't choose 8080, it's the port valve uses for CEF debugging, which we connect to. It is possible to change this port, I think, but it would require modifying the steam startup script. Decky generally tries to avoid system modification, so I'm not sure if we should. Probably better to test for it in the installer.

(Decky uses 1337 for itself, which could be changed but I don't think I've actually seen a collision with that yet)

https://github.com/OpenAsar/arrpc arrpc conflicts with Decky :/

CCF100 avatar Sep 09 '24 00:09 CCF100