Updating statuses (again) to reflect that there should no longer be an
active wpa_supplicant profile on Plucky, and to request that people
still running into issues attach the contents of their
/etc/apparmor.d/wpa_supplicant, which should no longer exist.
** Changed in: wpa (Ubuntu)
Status: Confirmed => Invalid
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
--
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:
apparmor appears to deny wpasupplicant on plucky, breaking wifi
Status in apparmor package in Ubuntu:
Fix Released
Status in wpa package in Ubuntu:
Invalid
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)
---
ProblemType: Bug
ApportVersion: 2.31.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
DistroRelease: Ubuntu 25.04
InstallationDate: Installed on 2025-01-15 (35 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20241216)
NonfreeKernelModules: zfs
Package: apparmor 4.1.0~beta5-0ubuntu2
PackageArchitecture: amd64
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.12.0-15-generic
root=UUID=8f848568-46b8-46b2-9ca3-37041ff7d0e3 ro quiet splash
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
ProcVersionSignature: Ubuntu 6.12.0-15.15-generic 6.12.11
Tags: package-from-proposed plucky wayland-session
Uname: Linux 6.12.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin nordvpn plugdev sudo users
_MarkForUpload: True
mtime.conffile..etc.apparmor.d.element-desktop: 2025-02-11T23:25:36.604214
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
