The check is not free, but it is an interesting idea to do this. I've
created a wishlist bug for it:
https://bugs.launchpad.net/ufw/+bug/1917325
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
CzBiX, ufw does not yet manage the nat table (though there have been a
couple of false starts). However, it does manage the FORWARD chain with
'ufw route' so it is possible for you to create a chain in the nat table
in /etc/ufw/before.rules, and then use ufw route for other things. This
is
Hi. A few things: ufw is capable of logging (see 'man ufw' the part
about 'ufw logging' as well as per rule logging with 'ufw ... log' or
'ufw ... log-all'. It is also capable of ipv6 (see /etc/default/ufw.
Also, gufw is a different project than ufw, but it sounds like the issue
you saw may be
Till, it allows quite a few things (from man capabilities):
CAP_SYS_NICE
* Raise process nice value (nice(2), setpriority(2)) and change the
nice value for arbitrary processes;
* set real-time scheduling policies for calling process, and set
scheduling
FYI, sponsored Alex's upload to hirsute-proposed where it is building.
Did the same for groovy-proposed and it is sitting in unapproved waiting
for the next steps of the SRU process.
** Changed in: iptables (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: iptables (Ubuntu)
FYI, 1.8.5-3ubuntu3 was uploaded to hirsute-proposed yesterday.
1.8.5-3ubuntu2.20.10.1 is in the unapproved queue for groovy-proposed.
Alex said he'd do the SRU paperwork.
** Changed in: iptables (Ubuntu Hirsute)
Status: Triaged => Fix Committed
--
You received this bug notification
FYI, this is part of the groovy upload in unapproved.
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
--
You received this bug notification because you are a member of Ubuntu
Touch
This has been uploaded to groovy and is currently in unapproved.
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Emilia Torino (emitorino)
--
You received this bug notification because you are a member
@Muhammad - can you run:
$ sudo /usr/share/ufw/check-requirements
and paste the results?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1726856
Title:
ufw does not start
** Changed in: iptables (Ubuntu)
Status: New => Fix Committed
** Changed in: iptables (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in
Removed the update_excuse and update_excuses tags based on Steve and
Alex's comments.
** Tags removed: update-excuse update-excuses
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
FYI, I removed the block-proposed tag since ubuntu6 fixes this bug.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895967
Title:
I uploaded 3.0.0~beta1-0ubuntu6 just now that should address this issue.
Thanks Christian for your debugging!
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
exists
---
Updated to add for Jamie:
$ snap version
snap2.44.2+20.04
snapd 2.44.2+20.04
series 16
ubuntu 20.04
kernel 5.4.0-21-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions
--
Mailing list: https://launchp
** Changed in: apparmor (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ap
FYI, there was a components mismatch where apparmor-notify pulled
python3-notify2 (and its Depends) into main. For now, I've demoted
apparmor-notify to universe and adjusted the seed (in practical terms,
the security team will fix bugs in apparmor-notify regardless of where
it lives). We might
Thanks! Uploaded:
https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu5
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
** Changed in: apparmor (Ubuntu)
FYI, I accidentally violated the FFe process and uploaded (with a
subsequent binary copy) to groovy-proposed. None of that migrated, so I
deleted what was in groovy-proposed and am now attaching the debdiff,
which has patches to pass proposed migration (we believe). Sorry for the
snafu.
** Patch
FYI, 3.0.0~beta1-0ubuntu3 should address the dbus autopkgtest issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895060
Title:
[FFe] apparmor 3 upstream release
FYI, the fix for the dbus issue is
https://gitlab.com/apparmor/apparmor/-/merge_requests/625. We're
preparing an ubuntu2 upload now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
FYI, we're looking at the autopkgtest dbus issue now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895060
Title:
[FFe] apparmor 3 upstream release
Status in apparmor
This will be fixed in the next apparmor upload.
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1880841
This will be fixed in the next apparmor upload.
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1887577
Thanks for the patch! I'll get this incorporated into the next apparmor
upload.
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification becau
You are right that there are two places this is defined: in
/etc/apparmor.d/abstractions/ubuntu-browsers.d/ubuntu-integration and in
/etc/apparmor.d/usr.bin.evince.
I'll adjust apparmor to fix ubuntu-integration to use the exo-open
abstraction.
There is an evince task though because we don't
Public bug reported:
To be filled in
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895060
I'm bumping the priority down to Undecided as its been almost 6 years--
it clearly isn't critical. :)
** Changed in: apparmor (Ubuntu)
Assignee: NYEIN LIN THU (mgnyein) => (unassigned)
** Changed in: apparmor (Ubuntu)
Importance: Critical => Undecided
** Changed in: ecryptfs-utils
** Also affects: libseccomp (Ubuntu Groovy)
Importance: Undecided
Assignee: Alex Murray (alexmurray)
Status: New
** Also affects: libseccomp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libseccomp (Ubuntu Bionic)
Importance: Undecided
ibus-daemon) | grep '/dbus'
ibus-daem 2973 jamie8u unix 0x 0t0 29606
@/tmp/dbus-oxKYpN30 type=STREAM
4. update the package in -proposed and perform '2' and '3'. The
IBUS_ADDRESSES should be the same as before
5. logout of unity, then log back in
6. $ grep IB
** Project changed: apparmor => apparmor (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1751677
This seems related:
* https://bugzilla.redhat.com/show_bug.cgi?id=1653068
* https://github.com/systemd/systemd/pull/11157
I can't say why the libseccomp update would change anything, though the
redhat bug shows an AVC denial, so I wonder if you see anything related
to systemd-resolved with
Note that 2.4.1-0ubuntu0.18.04.2 was previously in bionic and had been
since May of 2019 (2.3.1-2.1ubuntu4 is what bionic was released with,
but later updated to 2.4.1-0ubuntu0.18.04.2). 2.4.1-0ubuntu0.18.04.2 can
be found here:
We released UC16/xenial with a new enough apparmor (which was also
backported to trusty) so we can mark the snapd task as Invalid, which I
did just now.
** Changed in: snappy
Status: Incomplete => Invalid
** Changed in: snappy
Assignee: Jamie Strandboge (jdstrand) => (unas
@mm - that probably isn't the issue, but you can adjust
/etc/apparmor.d/local/usr.sbin.dhcpd to have:
@{PROC}/sys/net/ipv4/ip_local_port_range r,
and then do: sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.dhcpd #
yes, without local/
--
You received this bug notification because you are a
Marking as Invalid since the default firewall policy is working as
intended.
** Changed in: ufw (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Thank you for filing a bug.
The firewall policy is a combination of the default policy for each of
'incoming', 'outgoing' and 'routed' (forward) along with the policies
shipped in before{,6}.rules, after{,6}.rules and whatever gets added to
user{,6}.rules. Specifically, what is in
Marking as Invalid since the default firewall policy is working as
intended.
** Changed in: ufw (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Thank you for filing a bug.
The firewall policy is a combination of the default policy for each of
'incoming', 'outgoing' and 'routed' (forward) along with the policies
shipped in before{,6}.rules, after{,6}.rules and whatever gets added to
user{,6}.rules. Specifically, what is in
Sorry, I reran bionic and *focal* autopkgtests and there are now no
regressions. Running eoan again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1876055
Title:
SRU:
FYI, I reran the bionic and eoan autopkgtests and there are now no
regressions.
** Tags removed: verification-needed-bionic verification-needed-eoan
verification-needed-focal verification-needed-xenial
** Tags added: verification-done-bionic verification-done-eoan
verification-done-focal
FYI, I reran the bionic and eoan autopkgtests and there are now no
regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
libseccomp 2.4.3 (and
Sorry, I reran bionic and *focal* autopkgtests and there are now no
regressions. Running eoan again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
There isn't a snapd task (snap-seccomp is compiled against libseccomp
but it can't influence this behavior), so unassigning Ian and marking
that task as Invalid.
** Changed in: snapd
Status: Triaged => Invalid
** Changed in: snapd
Assignee: Ian Johnson (anonymouse67) => (unassigned)
FYI, I reran the xenial autopkgtests and they now pass.
** Tags removed: verification-done-focal
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
FYI, I reran the xenial autopkgtests and there are now no regressions.
** Tags removed: verification-done-bionic verification-done-eoan
verification-done-focal verification-done-xenial
** Tags added: verification-needed-bionic verification-needed-eoan
verification-needed-focal
FYI, I copied xenial-focal from the security-proposed ppa to -proposed.
Borrowing from the ubuntu-sru team's SRU verification text:
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback
FYI, I copied xenial-focal from the security-proposed ppa to -proposed.
Borrowing from the ubuntu-sru team's SRU verification text:
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback
FYI, a 2.4.3 SRU is in flight (by amurray), but looking at
https://github.com/seccomp/libseccomp/pull/180 (the fix for the bug),
https://github.com/seccomp/libseccomp/issues/187 (2.4.3 backports), and
code inspection, the fix for the bug is not in 2.4.3 and will come in
2.5.
The security team is
FYI, those re-runs passed and the package is green in
https://people.canonical.com/~ubuntu-archive/pending-sru.html. When
ubuntu-sru goes through the queue, this will be published.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
There is actually an SRU in progress for libseccomp:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
The autopkgtest failures seem unrelated. I triggered reruns just now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1872564
Title:
/proc/sys/kernel/random/boot_id rule
@Marco, this issue is not yet fixed in Focal. Marking back to Fix
Committed.
** Changed in: apparmor (Ubuntu Focal)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
@Sergio - assuming you are ok with my patch, do you still plan to follow
through on the SRU verification once it is accepted into focal-proposed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
@Sergio, I didn't see that you uploaded anything to the queue so to
expedite the SRU since there are a number of duplicates, I created a
smaller backport of the fix and uploaded it to focal-proposed just now:
@Till, the boot_id issue is being tracked here:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1721704
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"
snapd manages the security policies for snaps (and it will rewrite the
profiles at some point if you modify them yourself). You may install a
snap in devmode which puts apparmor in complain. Eg:
sudo snap install --devmode mysql-workbench-community
** Changed in: apparmor (Ubuntu)
Status:
This bug is marked fixed release. As I suggested in comment #13, please
file a new bug. This will allow you to use apport to upload any crash
information/etc that will assist developers in fixing this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: libseccomp (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
libseccomp 2.4.3 (and
Thanks for the debdiff Alex. Uploaded to groovy-proposed.
** Changed in: libseccomp (Ubuntu Groovy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
Rather than superseding 1:13.99.1-1ubuntu4 in groovy-proposed, I instead
based the changes in 1:13.99.1-1ubuntu5 on top of 1:13.99.1-1ubuntu4 to
address the CVE that was fixed in https://usn.ubuntu.com/4355-1/.
** Also affects: pulseaudio (Ubuntu Groovy)
Importance: High
Assignee:
Uploaded
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu5 to
groovy based on 1:13.99.1-1ubuntu4 from groovy-proposed.
** Changed in: pulseaudio (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
I'll apply the focal patch to what is in groovy-proposed.
** Changed in: pulseaudio (Ubuntu Groovy)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: pulseaudio (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification becau
FYI, the upload to bionic-proposed was superseded by
https://usn.ubuntu.com/4355-1/. Please rebase your changes on that and
reupload.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
FYI, the upload to focal-proposed was superseded by
https://usn.ubuntu.com/4355-1/. Please rebase your changes on that and
reupload.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Changed in: pulseaudio (Ubuntu Groovy)
Importance: High => Medium
** Changed in: pulseaudio (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: pulseaudio (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: pulseaudio (Ubuntu Bionic)
Importance: Undecided =>
*** This bug is a duplicate of bug 1872564 ***
https://bugs.launchpad.net/bugs/1872564
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
** This bug has been marked a duplicate of bug 1872564
/proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice
--
*** This bug is a duplicate of bug 1872564 ***
https://bugs.launchpad.net/bugs/1872564
This is a dupe of
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564 which,
AIUI, the server team will be performing an SRU for.
** This bug has been marked a duplicate of bug 1872564
** Description changed:
- This was reported via the snapcraft forum:
+ This was reported via the snapcraft forum[1]:
On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2
$ lsb_release -d
Description: Ubuntu 18.04.4 LTS
$ scmp_sys_resolver -a aarch64 163
getrlimit
$
Public bug reported:
This was reported via the snapcraft forum:
On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2
$ lsb_release -d
Description:Ubuntu 18.04.4 LTS
$ scmp_sys_resolver -a aarch64 163
getrlimit
$ scmp_sys_resolver -a aarch64 getrlimit
163
focal amd64, libseccomp
FYI, there is a pending update that will go out either tomorrow or early
next week. Please base your next upload on this update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I confirmed that https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html shows no autopkgtest regression for
xenial.
I also ran through the TEST CASE for this bug and xenial passed. Marking
verification-done-xenial
** Tags removed: verification-failed-xenial
I confirmed that https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html shows no autopkgtest regression for
bionic.
I also ran through the TEST CASE for this bug and bionic passed. Marking
verification-done-bionic.
** Tags removed: verification-failed
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
talled snaps back to full functionality.
Previously, when running any snap I would receive the following in the
terminal:
---
cannot change profile for the next exec call: No such file or directory
snap-update-ns failed with code 1: File exists
---
Updated to add for Jamie:
$
The abstraction is meant to cover the client, not systemd internal
specifics. A client simply accessing that DBus API won't need it and a
client simply accessing those sockets won't need it. It very well might
be that a profiled application is using some *ctl command from systemd
that would need
I will update the policy for the write access. I suggest removing the
crash file in /var/crash, then if you see the crash again, file a new
bug with the crash information (eg, apport-cli if on a server) so it can
be analyzed.
--
You received this bug notification because you are a member of
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1871615
Title:
package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of
file on stdin at
Foundations, it seems like unattended-upgrades should be smarter with
conffile changes (honestly, I thought it was)? Note, the security also
saw this in https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1871261.
Is this a regression?
** Also affects: unattended-upgrades (Ubuntu)
Importance:
Per https://launchpadlibrarian.net/473598993/DpkgHistoryLog.txt,
unattended-upgrades is running on this system.
Per
https://launchpadlibrarian.net/473598999/modified.conffile..etc.apparmor.d.abstractions.base.txt,
/etc/apparmor.d/abstraction/base was modified to include:
# adds networking to
for Jamie:
$ snap version
snap2.44.2+20.04
snapd 2.44.2+20.04
series 16
ubuntu 20.04
kernel 5.4.0-21-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post
or directory
snap-update-ns failed with code 1: File exists
---
Updated to add for Jamie:
$ snap version
snap2.44.2+20.04
snapd 2.44.2+20.04
series 16
ubuntu 20.04
kernel 5.4.0-21-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug
ile or directory
snap-update-ns failed with code 1: File exists
---
Updated to add for Jamie:
$ snap version
snap2.44.2+20.04
snapd 2.44.2+20.04
series 16
ubuntu 20.04
kernel 5.4.0-21-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/appar
full functionality.
Previously, when running any snap I would receive the following in the
terminal:
---
cannot change profile for the next exec call: No such file or directory
snap-update-ns failed with code 1: File exists
---
Updated to add for Jamie:
$ snap version
snap2.
all: No such file or directory
snap-update-ns failed with code 1: File exists
---
Updated to add for Jamie:
$ snap version
snap2.44.2+20.04
snapd 2.44.2+20.04
series 16
ubuntu 20.04
kernel 5.4.0-21-generic
To manage notifications about this bug go to:
https://bugs.laun
for Jamie:
$ snap version
snap2.44.2+20.04
snapd 2.44.2+20.04
series 16
ubuntu 20.04
kernel 5.4.0-21-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post
is enough
to bring installed snaps back to full functionality.
Previously, when running any snap I would receive the following in the
terminal:
---
cannot change profile for the next exec call: No such file or directory
snap-update-ns failed with code 1: File exists
---
Updated to
Now that there are no apparmor denials, this sounds like something for
the server team to take a look at. Can you file a new bug since this one
was used to address the apparmor denials? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Thank you for reporting a bug and helping to make Ubuntu better.
Based on https://launchpadlibrarian.net/473334677/DpkgTerminalLog.txt:
Preparing to unpack .../archives/ufw_0.36-6_all.deb ...
Unpacking ufw (0.36-6) over (0.36-5) ...
Setting up ufw (0.36-6) ...
Configuration file
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1796911
Title:
libnss-systemd was denied
4.4.1-2.1ubuntu4 was uploaded for the above. Please let us know if it
doesn't fix the issue for you.
** Changed in: isc-dhcp (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
FYI, I submitted https://github.com/snapcore/snapd/pull/8443 for this.
** Changed in: snapd
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
FYI, I added these accesses in
https://github.com/snapcore/snapd/pull/8443
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => In Progress
** Changed in: snapd
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You re
.
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu)
Status: New => In Progress
** Changed in: isc-dhcp (Ubuntu)
Milestone: None => ubuntu-20.04
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) => Jamie Strandbo
c call: No such file or directory
snap-update-ns failed with code 1: File exists
---
Updated to add for Jamie:
$ snap version
snap2.44.2+20.04
snapd 2.44.2+20.04
series 16
ubuntu 20.04
kernel 5.4.0-21-generic
To manage notifications about this bug go to:
https://bugs.launchp
** Changed in: snapd
Status: In Progress => Fix Released
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
* Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1848919
Title:
[snap] Permi
** Changed in: apparmor (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jami
pparmor (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: apparmor (Ubuntu Focal)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to appa
101 - 200 of 1891 matches
Mail list logo
