Hi all
After getting into this, today I performed a full upgrade from oneiric and all
went well, the wifi still working. Before the distro upgrade I upgraded
wpasupplicant to the latest version in the repo (proposed?) but strangely it
was detected as not original package. After that no more prob
@xypron:
policy can be shipped as part of the package, or part of the system
policy. Atm unless there is a good reason, or an active package
maintainer who wants to maintain the policy, profiles are being shipped
as part of system policy, in the apparmor package.
--
You received this bug notific
The broken profile located in /etc/apparmor.d/wpa_supplicant should have
been removed by the upgrade to 4.1.0~beta5-0ubuntu5. Was it still there
on your system after the upgrade?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Hello Ryan,
In my logs I see:
2025-02-23T08:21:14 boot
2025-02-23T08:24:21 connected via Ethernet cable
2025-02-23T08:48:08 update python3-libapparmor:amd64 (4.1.0~beta5-0ubuntu2,
4.1.0~beta5-0ubuntu5)
2025-02-23T08:50Sending information for LP #2099789 via apport-report
2025-02-23T09:08:29
Hi Heinrich,
Could you also confirm how you constructed the above AppArmor profile
for wpa_supplicant? Did you create it based on the broken wpa_supplicant
profile shipped in the earlier AppArmor package, or did you create it
some other way?
--
You received this bug notification because you are
Hi Heinrich. Did you try rebooting after upgrading to 4.1.0~beta5-0ubuntu5?
The profile could still be loaded in the kernel thus enforcing restrictions
unless rebooting or manually unloading the profile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Apparmor 4.1.0~beta5-0ubuntu5 did not solve the problem for me.
** Changed in: apparmor (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098838
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098838
Title:
apparm
Please, find appended an apparmor file that works for me to work around
the issue.
I guess the problem should be fixed in source package wpa.
** Also affects: wpa (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "usr.sbin.wpa_supplicant"
https://bugs.launchpad.net/ub
Switching this to "Fix Released" now that the 0ubuntu5 release is out
that disables the profile - feel free to switch back if you're still
encountering issues even on that release.
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification bec
Hi Georgia, thanks for the link -- I'll add some details there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098838
Title:
apparmor appears to deny wpasupplicant on plucky, breaking wifi
To manag
Hi Dave
There's a new apparmor_4.1.0~beta5-0ubuntu5 available in plucky-proposed that
should remove the wpa_supplicant apparmor profile. We decided to disable it by
default for now in Ubuntu
I added a comment in the upstream MR for the profile fix, feel free to add more
details there if you wish
Sorry to be the bearer of bad news: unfortunately this still appears
broken on certain platforms. Specifically, testing a fresh plucky image
on the Raspberry Pi, the wifi interface was recognized but not
configured:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
This bug was fixed in the package apparmor - 4.1.0~beta5-0ubuntu4
---
apparmor (4.1.0~beta5-0ubuntu4) plucky; urgency=medium
* Add patch to fix sbuild unshare breakage caused by the new
unshare-userns-restrict profile (LP: #2098906)
- d/p/u/sbuild_mr_1555.patch
apparmor (4.
Hi Khairul.
Unfortunately the fix was not complete and there's a 4.1.0~beta5-0ubuntu5 on
the way. What you can do now is unload the profile and remove it.
# apparmor_parser --remove /etc/apparmor.d/wpa_supplicant
# rm /etc/apparmor.d/wpa_supplicant
--
You received this bug notification because
updated to 4.1.0~beta5-0ubuntu4 , anything i should do after upgrading
the packages?
** Attachment added: "Screenshot From 2025-02-20 15-58-30.png"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2098838/+attachment/5858960/+files/Screenshot%20From%202025-02-20%2015-58-30.png
--
You
** Changed in: apparmor (Ubuntu)
Milestone: None => ubuntu-25.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098838
Title:
apparmor appears to deny wpasupplicant on plucky, breaking wifi
To
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098838
Title:
apparmor appears to deny wpasupplicant on plucky, breaking wif
apport information
** Tags added: apport-collected package-from-proposed plucky wayland-
session
** Description changed:
2/19/25 4:44 PM user@1000.service NM.DeviceError: Scanning not
allowed while unavailable
Stack trace:
_promisify/proto[asyncFunc]/https://bugs.launchpad.ne
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ryan Lee (rlee287)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/209883
The first denial I am seeing is for netlink. So
network (create) netlink raw,
I am assuming once it is allowed creation of the netlink socket their
will be addition permissions needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Seems like the new wpa_supplicant protocol will need rules allowing read
access to /sys/devices/pci*:*/*:*:*.*/ieee80211/phy*/** and to allow
dgram socket creation, but there may be other accesses we might have
missed that would be needed to unbreak the profile. For now, we'll
proceed by disabling
Feb 19 16:34:01 NetworkManager[2205]: [174841.7226] manager:
rfkill: Wi-Fi hardware radio set enabled
Feb 19 16:34:01 systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill
Switch Status...
Feb 19 16:34:01 systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill
Switch Statu
** Summary changed:
- wifi unavailable
+ apparmor appears to deny wpasupplicant on plucky, breaking wifi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098838
Title:
apparmor appears to deny wpasup
24 matches
Mail list logo
