Skype snap generates way too much apparmor violations

snap
1 
Apr 28 15:13:32 ivan-dell kernel: [ 6179.897324] audit: type=1400 audit(1619579612.267:12211): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/charge_full" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6179.897326] audit: type=1400 audit(1619579612.267:12212): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/capacity" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6179.927634] audit: type=1400 audit(1619579612.299:12213): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/charge_full" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6179.927636] audit: type=1400 audit(1619579612.299:12214): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/capacity" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6179.958426] audit: type=1400 audit(1619579612.331:12215): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/charge_full" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6179.958429] audit: type=1400 audit(1619579612.331:12216): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/capacity" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6180.002915] audit: type=1400 audit(1619579612.375:12217): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/charge_full" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6180.002944] audit: type=1400 audit(1619579612.375:12218): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/capacity" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6180.023952] audit: type=1400 audit(1619579612.395:12219): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/charge_full" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:32 ivan-dell kernel: [ 6180.023955] audit: type=1400 audit(1619579612.395:12220): apparmor="DENIED" operation="open" profile="snap.skype.skype" name="/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/capacity" pid=17029 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 28 15:13:37 ivan-dell kernel: [ 6184.911140] kauditd_printk_skb: 302 callbacks suppressed

What would be a proper place to report it so that access to battery details and network interfaces details were allowed to make it calm?

2

This is unexpected. Is there a /etc/apparmor.d/usr.bin.snap file in your system? If it exists, can you identify which package owns this file by running dpkg -S /etc/apparmor.d/usr.bin.snap?

3

There is no such file on my system. And the problem is not unique: it’s exactly the same on my wife’s laptop (a totally independent and configured separately system).

4

i guess the skype snap needs to add the hardware-observe plug to the plugs definition …

5

That is great, how do I (as a user) do that?

6

you can not, but i would hope by now that someone reported it to skype since may so they can add it to their snap (it is a one-line change in the package metadata), if you are unsure if one of the people in this thread have reported it yet, perhaps report it again …

7

Hello - I fixed those apparmor errors (same as what you got) and the version of skype I’m using is skype 8.106.0.210 305 latest/stable skype✓ - which was released a few days ago.

I’m not sure how to share that fix into the skype snap - I don’t see a git repo for it, etc.

So I created my own git repo that fixes this issue: https://github.com/AJRepo/apparmor-skype