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

[BUG] Decky Loader tab does not appear in quick setting specifically in Offline Mode.

Open Ornithorax opened this issue 10 months ago • 9 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

Power on the Steam Deck from a full shutdown, making sure there is no WiFi that the Deck could connect to.

Wait for the Deck to boot in offline mode.

Observe the lack of the Decky Loader icon in the quick settings menu.

This seems to be caused by the Steam Deck offline mode itself, rather than the lack of internet access, as the icon will appear even if the Deck is connected to a nonfunctional WiFi network.

Expected Behaviour

The Decky Loader icon should appear in the quick settings menu.

SteamOS version

SteamOS 3.5.17 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

Ornithorax avatar Apr 15 '24 16:04 Ornithorax

the same exact thing has been happening to me every time I'm offline on a flight to work 😞, i hope theres an easy fix.

denver8989 avatar Apr 16 '24 00:04 denver8989

Exact same issue here. Restarting the steamdeck with wifi turned off removes the decky quick setting. Plugins still seem to run in the background . Turning on wifi and connecting to any wifi network brings back the quick setting after a restart.

Found out the hard way on the plane a few days ago. Tried reinstalling, switching between beta and stable. Still the same.

Hereticofdune avatar Apr 28 '24 06:04 Hereticofdune

the bigest issue for me here is I'm actually running bazite os on a lenovo legion go so, without decky the plugins the make controls tdp and fan control work go poof and I'm then screw. seems the trick is to make sure to go into stand by mode always to avoid this from happening on my flights to work.

denver8989 avatar Apr 28 '24 06:04 denver8989

Ah, you know what I am on Bazzite also - this may be a Bazzite issue ( not sure about OP). I'll go take a look at the Bazzite forums and maybe make a post there. Don't want to bother decky devs if the issue isn't present on vanilla steamdeck.

Hereticofdune avatar Apr 28 '24 06:04 Hereticofdune

I've been told its a decky issue that also occurs on steam decks, and i believe the person who raised this is posting this issue for a steam deck. again not really a game breaking issue on steam decks but if your system relies on decky to work properly yikes 😬.

denver8989 avatar Apr 28 '24 07:04 denver8989

Also on Bazzite but on a GPD device, same thing, know it’s not too helpful but if anyone has found a solution I’d appreciate any info.

AkeMang avatar Jun 09 '24 21:06 AkeMang

I noticed that the pre-release version of Decky Loader appears to be trying to address this issue. I updated to the pre-release version and am still getting the same behavior. Decky does not appear to load until I turn back on my WiFi, only then does it appear in the quick-settings. Just an FYI

Hereticofdune avatar Jul 03 '24 05:07 Hereticofdune

I can confirm that this happens on my ROG Ally which is running the latest version of Bazzite (3.5.0 at the time of writing) I've switched to the Pre-Release version of decky (3.0.0-pre4), and the issue persists.

Ravmyster1121 avatar Jul 16 '24 01:07 Ravmyster1121

The initial post maybe didn't describe it exactly right, but this issue occurs when there is no IP address assigned to any network device, other than the loopback address (127.0.0.1) on the loopback interface. Not sure if Decky Loader doesn't attempt to use the loopback address or is unable to do so.

As a workaround, adding a dummy interface with an IP address that is not in the normal loopback range makes Decky Loader work without any other network connection being connected when Steam starts. It also seemed to work to have the IP address added to the loopback interface, but I could not figure out how to have this applied properly to the loopback interface on boot with the distro I'm using (Bazzite).

ShadowFlare avatar Aug 19 '24 12:08 ShadowFlare