-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't handle WiFi #271
Comments
Wifi settings ave arrived within Cosmic settings app but the wifi applet is still not working properly, same as previously described. |
How is your networking configured? |
in configuration.nix, I have simply :
and nothing about it in my specialisation.nix file How should it be? On a different but linked issue, upstream, I got this answer, pop-os/cosmic-epoch#976 (comment), can it be related? |
I'll try adding something like this :
|
It has indeed solved this issue pop-os/cosmic-epoch#976 (comment) and also it has added a wifi option among applets but it doesn't feel quiet right (not very integrated. I'd be interested to see how it should look like by the way). is the new wifi option among applets is the same as before : no icon and impossible to switch wifi toggles. |
I have the same issue. I cannot toggle anything with the Cosmic network app, but I can change network seetings either via nmcli or via the network settings page in cosmic. I found the following error, which I'm guessing is the cause:
uid 1000 is my user, and I am in both wheel and the networkmanager group, and I'm not sure why this permissions error is occurring.
|
The issue is still here on alpha 3 |
I think I found out my issue. I deleted all past connection setting that were containing a WEP wifi password, reboot and now the network applet display and is working. |
Hello,
I face the same issue as #107
Wifi connects automatically but I can't handle WiFi from Cosmic. Bluetooth works out of the box.
The Wifi toggle is there, but it is grayed out, and I can't switch it and I can't find any wifi settings.
The text was updated successfully, but these errors were encountered: