Bug or Feature?

So throughout the morning I’ve been struggling to consistently get wifi to connect, it works right after flashing but after setting it up and rebooting it fails scanning for networks. Well I ended up figuring out the culprit, its because I disabled the “start network on boot” setting. Now my question is, is this normal behavior of this setting? Because in the previous Goose release I had this setting disabled and it worked as I assumed it did: it wouldn’t connect to any network on boot but I could manually go into the connectivity configuration and connect. But on this new update it doesn’t work like this, it still doesn’t connect on boot as expected, but attempting to manually connect in the connectivity configuration doesn’t work, it just instantly fails scanning for networks. Is it supposed to be like this? Thank you guys for all your awesome work btw!

This is fixed in the upcoming 2508.2 Silly Goose patch release.

1 Like

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.