I'm not familiar with mysql-workbench-community, but looking at the logs
I see:
May 14 17:44:33 owen-AOD255 kernel: [ 181.312508] audit: type=1400
audit(1589474673.710:1024): apparmor="DENIED" operation="connect"
profile="snap.mysql-workbench-community.mysql-workbench-community"
name="/run/uuidd/request" pid=3579 comm="mysql-workbench"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
This issue was fixed in a recent commit to snapd, but it hasn't reached
the stable channel yet (it should be in snapd 2.45). You can either:
* 'sudo snap install --devmode mysql-workbench-community' to work around the
issue and put apparmor into complain mode
* 'sudo snap refresh snapd --edge' to pull in the edge build of snapd which has
the fix
If choosing the former, when 'snap version' reports 2.45, you can
install the snap in strict mode (omit --devmode). If the latter, when
'snap info snapd' reports that 2.45 is in the stable channel, run 'sudo
snap refresh snapd --stable' to start tracking stable again.
This is not a bug in apparmor, but instead snapd. Triaging the bug as
such.
** Package changed: apparmor (Ubuntu) => snapd (Ubuntu)
** Changed in: snapd (Ubuntu)
Importance: Undecided => Medium
** Changed in: snapd (Ubuntu)
Status: New => In Progress
** Changed in: snapd (Ubuntu)
Milestone: None => focal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878814
Title:
apparmor stays active even when the service is disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878814/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs