** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: gnome-shell (Ubuntu)
Assignee:
Without the polkit rules, you'll still be able to connect to the wifi
but the connection won't persist after logging-in: it will only be
usable from the login screen, which is quite useless.
Similarly the gnome-initial-setup user is allowed to make system-wide
changes because it wouldn't make sens
That's great, thank you Alessandro!
>https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3646
I wonder if they agree about this change, isn't somewhat overriding the
security?
If the polkit rules are removed, because let's say someone don't like that
will this still throw an error at us
I've submitted these fixes upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3646
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/276
I'll gather some feedback from upstream before backporting as patches.
--
You received this bug notification because you are a member of U
** Changed in: network-manager (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098016
Title:
Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new
After the discussion with Alessandro:
I fixed the ExecStart and now it run with control file
root@desktop-noble:~# ps aux|grep keyring │.service: Deactivated successfully.
gdm 1836 0.0 0.1 314312 9600 ? Ssl 15:39 0:00 /usr/bin/gnome-keyring-daemon
--foreground --
components=secrets --control-dire
Thanks Alesto due to private message, I fixed my previous comment and
added
ExecStart= in override to unset it first
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098016
Title:
Ubuntu 24.04 WiFi f
I attached sos report
** Attachment added:
"sosreport-desktop-noble-lp-2098016-2025-02-17-zzlaapp.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2098016/+attachment/5858212/+files/sosreport-desktop-noble-lp-2098016-2025-02-17-zzlaapp.tar.xz
--
You received this bug n
Interesting observation in noble in contrary to jammy, the keyring runs
with two components secrets,pkcs11, instead only secrets
root@desktop-noble:~# ps aux|grep keyrin
gdm 5468 0.0 0.1 314312 9728 ?Ssl 11:12 0:00
/usr/bin/gnome-keyring-daemon --foreground --components=pkcs
** Tags added: udeng-6076
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098016
Title:
Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network
To manage notifications about this bug go
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you a
I checked again and it seems that dbus-daemon goes zombie
gdm 1927 0.0 0.0 0 0 tty1 Z+ 15:42 0:00
[dbus-daemon]
The keyring seems to be running with the proper options
root@desktop-noble:~# ps aux|grep keyring
So I did tests on Jammy, installed fresh Ubuntu Jammy from ISO on the VM
instance and attached the WiFi device.
Initially it asked me for admin password to change the network settings.
In Jammy the polkit (<0.106) still relies on pkla files to add the proper
privileges, instead of Javascript-cod
** Package changed: gdm3 (Ubuntu) => network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098016
Title:
Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network
To man
** Description changed:
Steps to reproduce
1. Create LXD VM desktop-noble
lxc init --vm ubuntu:24.04 desktop-noble
2. Passthrough wifi device, in my case Intel Wifi via PCI works fine, some
USB devices can have problem with initialization
lxc config device add desktop-noble wifipci p
15 matches
Mail list logo
