** Changed in: chromium-browser (Ubuntu)
Status: Expired => New
** Tags added: snap
** Summary changed:
- apparmor warning when using chromedriver snap
+ [snap] apparmor warning when using chromedriver
--
You received this bug notification because you are a member of Desktop
Packages,
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
True, but I don't see the harm of allowing an application to access
information about his own process. Anyway as long as the log don't get
flooded anymore, I will be happy :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
If its just log flooding then denying access would get rid of the
logging without adding extra permissions. ie.
deny owner @{PROC}/@{pid}/mem r,
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
It is about log flooding, I did not see any impact otherwise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1949466
Title:
apparmor warning when using chromedriver snap
Indeed, this change will get overwritten every time the snap is updated.
Are you observing functional regressions caused by this denial? Or is
the problem only about log flooding?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
6 matches
Mail list logo
