[Touch-packages] [Bug 2074070] Re: unable to get WPA supplicant status via wpa-cli utility from a snap

2024-08-05 Thread Philip Meulengracht
So I looked into this and the observations made in this post is correct. It's because the default path of the wpa_cli client socket made is in /tmp (they use AF_UNIX sockets, and UDP protocol - this means the client socket must bind a visible place for the server) /tmp is obviously not visible out

[Touch-packages] [Bug 2074070] Re: unable to get WPA supplicant status via wpa-cli utility from a snap

2024-08-06 Thread Philip Meulengracht
Just as an added information, providing the switch `-s /run/wpa_supplicant` with the network-control interface connected should work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bu

[Touch-packages] [Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group

2024-09-04 Thread Philip Meulengracht
Hey! Sorry for the slow response from the Core team, I can verify this is now working with passwd in proposed. I was able to add a user with --extrausers and --groups switches together. It no longer fails on locking /etc/groups -- You received this bug notification because you are a member of Ub