NixOS / nixpkgs

Nix Packages collection & NixOS
MIT License
17.34k stars 13.58k forks source link

xfce4 nm-connection-editor's WPA2 wifi passwords do not persist through reboots #27208

Open 0xABAB opened 7 years ago

0xABAB commented 7 years ago

Issue description

XFCE 4.12 won't remember WPA2 Personal password through reboots, unlike Plasma5, even though the password is saved via some dialog.

This makes XFCE4 on NixOS unattractive to use, because the password needs to be typed in every time the machine is booted.

Steps to reproduce

  1. Start nm-connnection-editor in an XFCE4 session on a terminal
  2. Set the correct password (if you type a password which conforms the right grammar you will see a message printed on the terminal (** Message: Connection validates and can be saved ))
  3. Press the Save button.
  4. Reboot
  5. Login to XFCE 4 again.

Technical details

17.03.1482.1b57bf274a (Gorilla)

emmanuelrosa commented 7 years ago

Is this perhaps an upstream problem?

stale[bot] commented 4 years ago

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

  1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse.
  3. Ask on the #nixos channel on irc.freenode.net.
rantlivelintkale commented 1 year ago

I know the issue is stale, but just ran to this problem myself when switching from Plasma to xfce.

Simply deleting the connection completely with nm-connection-editor and reconnecting fixed it. I assume this has something to do with how the passwords are saved.

Should this be documented in the wiki or elsewhere?

Not sure if this is really a problem that can be fixed upstream easily. (delete all connections if user has switched their nm connection manager?)