I normally use Ethernet and my Wifi stopped working today after a
reboot. I thought I had rebooted after installing the updated gnome-
keyring packages. I so far haven't figured out what packages triggered
the Wifi not working.
I am getting some apprmor denials related to wpasupplicant when I turn
on wifi.
apparmor="DENIED" operation="create" class="net"
profile="wpa_supplicant" comm="wpa_supplicant" family="netlink"
sock_type="raw" protocol=0 requested="create" denied="create"
This is not fixed for me by installing an older version of appamor.
apparmor was updated today also.
It looks clear to me that this is not a gnome-shell bug though.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Critical
** Package changed: gnome-shell (Ubuntu) => apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2098838
Title:
wifi unavailable
Status in apparmor package in Ubuntu:
New
Bug description:
2/19/25 4:44 PM user@1000.service NM.DeviceError: Scanning not
allowed while unavailable
Stack trace:
_promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:453:45
@resource:///org/gnome/shell/ui/init.js:21:20
### Promise created here: ###
_scanDevice@resource:///org/gnome/shell/ui/status/network.js:1821:22
_scanDevices/<@resource:///org/gnome/shell/ui/status/network.js:1844:35
_scanDevices@resource:///org/gnome/shell/ui/status/network.js:1844:21
_startScanning@resource:///org/gnome/shell/ui/status/network.js:1855:14
NMWirelessToggle/<@resource:///org/gnome/shell/ui/status/network.js:1789:22
_callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10
open@resource:///org/gnome/shell/ui/quickSettings.js:476:14
_init/<@resource:///org/gnome/shell/ui/quickSettings.js:226:61
@resource:///org/gnome/shell/ui/init.js:21:20
2/19/25 4:44 PM user@1000.service NM.DeviceError: Scanning not
allowed while unavailable
Stack trace:
_promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:453:45
@resource:///org/gnome/shell/ui/init.js:21:20
### Promise created here: ###
_scanDevice@resource:///org/gnome/shell/ui/status/network.js:1821:22
_scanDevices/<@resource:///org/gnome/shell/ui/status/network.js:1844:35
_scanDevices@resource:///org/gnome/shell/ui/status/network.js:1844:21
_startScanning/this._scanTimeoutId<@resource:///org/gnome/shell/ui/status/network.js:1852:22
@resource:///org/gnome/shell/ui/init.js:21:20
problem occurs/noticed after recent upgrade of the packages:
libpam-gnome-keyring:amd64 (46.2-1, 48~beta-3)
gnome-keyring:amd64 (46.2-1, 48~beta-3)
gnome-keyring-pkcs11:amd64 (46.2-1, 48~beta-3)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2098838/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
