On Fri, 23 Mar 2018, Simon McVittie wrote:
it would be unexpected for someone finding a machine with a
locked GNOME session, logged in as a user with netdev privileges, to be
able to reconfigure the network without first unlocking the session!
I could make the same argument that it is unexpect
On Thu, 22 Mar 2018 at 21:12:16 -0400, Matthew Gabeler-Lee wrote:
> This actually looks like it might be a bug in gnome-shell, and still present
> in 3.28. This silly-looking(?) bit of logic is present there in
> js/ui/status/network.js:
>
> _sessionUpdated() {
> let sensitive = !Main
Package: gdm3
Version: 3.22.3-3+deb9u1
Followup-For: Bug #891599
This actually looks like it might be a bug in gnome-shell, and still present
in 3.28. This silly-looking(?) bit of logic is present there in
js/ui/status/network.js:
_sessionUpdated() {
let sensitive = !Main.sessionMode
Package: gdm3
Version: 3.22.3-3+deb9u1
Severity: normal
Based on the policy-kit settings, I would expect that adding the Debian-gdm
user to the netdev group (and restarting gdm3 or rebooting) to allow me to
control network connections from the greeter (AKA login screen). For
example, if a VPN nee
4 matches
Mail list logo
