[SRU] Add AssumedAppArmorLabel to fwupd service
Bug #1852485 reported by
Ken VanDine
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fwupd (Ubuntu) |
Fix Released
|
Low
|
Ken VanDine | ||
Bionic |
Fix Released
|
Low
|
Ken VanDine | ||
Disco |
Won't Fix
|
Low
|
Ken VanDine | ||
Eoan |
Fix Released
|
Low
|
Ken VanDine | ||
fwupd-signed (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In order for strictly confined snaps to work with the host's fwupd we need to add the AssumedAppArmor
[Impact]
* Without this label, strictly confined snaps can not work with the host's fwupd service
[Test Case]
* snap install --edge gnome-firmware
* snap connect gnome-firmware:
* snap run gnome-firmware
* Expected results: Display devices with upgradable firmware
[Regression Potential]
* There should be no potential for regression, this is adding an optional label that will not effect other services communicating with the fwupd service.
Changed in fwupd (Ubuntu): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
Changed in fwupd (Ubuntu Bionic): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
Changed in fwupd (Ubuntu Disco): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
Changed in fwupd (Ubuntu Eoan): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
Changed in fwupd (Ubuntu): | |
importance: | Undecided → Low |
Changed in fwupd (Ubuntu Bionic): | |
importance: | Undecided → Low |
Changed in fwupd (Ubuntu Disco): | |
importance: | Undecided → Low |
Changed in fwupd (Ubuntu Eoan): | |
importance: | Undecided → Low |
Changed in fwupd (Ubuntu Eoan): | |
status: | New → Fix Committed |
Changed in fwupd-signed (Ubuntu): | |
status: | New → Fix Released |
Changed in fwupd (Ubuntu Disco): | |
status: | New → Won't Fix |
Changed in fwupd-signed (Ubuntu Disco): | |
status: | New → Won't Fix |
To post a comment you must log in.
Focal has the fix coming in during Debian unstable sync. Setting this task to fix committed.