"Upstream apparmor has moved to defaulting the location to
/var/cache/apparmor. But Ubuntu has yet to make this move."
As mentioned in comment #1: "2.13.2-9ubuntu1 moved the cache dir to
/var/cache/apparmor". Ubuntu 19.04+ is using /var/cache/apparmor.
--
You received this bug notification
I'll take a look at this when preparing the next release, which should
be in the coming weeks.
** Changed in: ufw (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: ufw (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Thank you for using Ubuntu and reporting a bug.
Please note that 'sudo ufw disable' will flush the ufw chains and make
them all 'pass through' (ie, think of them as NOPs) until reboot. On
reboot, ufw won't run and even the pass through chains won't be added.
Furthermore, unless MANAGE_BUILTINS
libreoffice ships this profile, so the bug should be tracked there.
** Package changed: apparmor (Ubuntu) => libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
This was fixed upstream in 61c27d8808f0589beb6a319cc04073e8bb32d860
** Changed in: apparmor
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.
Keeping the profiles in the running kernel is by design since there
might be processes that are still running under the profile on package
removal. dpkg doesn't do anything to guarantee that executables that the
package ships aren't running, so we can't reasonably unload the
profiles. Marking
John, what do you think about Seth's question in
https://bugs.launchpad.net/apparmor/+bug/1667751/comments/5?
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Incomplete
--
You received this bug notification because you are a
This was fixed in 2.13.3-5ubuntu1 which added upstream-tests-mult-mount-
bump-size-of-created-disk.patch
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Ultimately this is a kernel issue and the limitations it puts on
apparmor for tracking files with disconnected paths. There isn't
anything that the apparmor package or abstractions can do to help with
this, but people can update their profiles to use
flags=(attach_disconnected), as mentioned. For
Today, people experiencing this error need to use
flags=(attach_disconnected) in the profile. Eg:
/path/to/thing flags=(attach_disconnected) {
...
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
@Matyáš, this configuration seems like something you added:
/etc/dovecot/conf.d/10-master.conf
service auth {
unix_listener auth-userdb {
mode = 0666
user = vmail
group = mail
}
unix_listener /var/spool/postfix/private/auth {
mode = 0666
user =
This is the result of a disconnected path with how the container is
being setup. This isn't something that should be added to the apparmor
abstractions. Ultimately this is a kernel issue and the limitations it
puts on apparmor for tracking files with disconnected paths. There isn't
anything that
Marking the dovecot task as Invalid since it doesn't ship the profiles.
** Changed in: dovecot (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.
** Changed in: apparmor (Ubuntu)
Status: New => 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
These were only needed for bionic and we can drop in focal.
** 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.
The path to vivaldi indicates that the application you are trying to
launch is not in the Ubuntu repositories. To accommodate this sort of
thing, apparmor profiles in Ubuntu ship files in /etc/apparmor.d/local
for admins to modify. I suggest adding this to
/etc/apparmor.d/local/usr.bin.evince:
*** This bug is a duplicate of bug 1848567 ***
https://bugs.launchpad.net/bugs/1848567
I'm going to mark the linux task as Invalid and then mark as a dupe of
bug 1848567
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: apparmor (Ubuntu)
Status: New
The apparmor package provides this file:
$ dpkg -S /etc/apparmor.d/abstractions/mysql
apparmor: /etc/apparmor.d/abstractions/mysql
It seems the file was accidentally deleted. Recreating it in the manner
you did is the proper way to resolve the issue.
** Changed in: apparmor (Ubuntu)
2.13.2-9ubuntu1 moved the cache dir to /var/cache/apparmor.
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Package changed: apparmor (Ubuntu) => firefox (Ubuntu)
--
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/1482852
Title:
apparmor profile usr.bin.firefox missing
@Gunnar - I am preparing the focal upload now, though there is a parser
bug (bug 1856738) which means I cannot use @{HOME} in the rule and
instead hardcode /home/*/. This will cover all typical situations (ie,
not the atypical /root/.cache/ibus...) except when the user updates
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Triaged
** Changed in: apparmor (Ubuntu)
Status: New => Triaged
** Changed in: apparmor
Importance: Undecided => Medium
** Changed in: apparmor (Ubuntu)
Note, there is a spread test in snapd that checks for if the mediation
patches are dropped (or added). While it is fine for
https://launchpad.net/bugs/1856054 to be fast tracked, this pulseaudio
bug should not be marked as Fix Released before the end of year break
unless you coordinate with the
Installing 1:8.0-0ubuntu3.11 from xenial-proposed, the test plan and
James' addition for mediation is preserved across snapd restart all
works as expected. Marking as verification done.
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if
Installing 1:11.1-1ubuntu7.5 from bionic-proposed, the test plan and
James' addition for mediation is preserved across snapd restart all
works as expected. Marking as verification done.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug
** 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
** Changed in: ufw (Ubuntu)
Status: New => Triaged
** Changed in: ufw (Ubuntu)
Importance: Undecided => Medium
** Also affects: ufw
Importance: Undecided
Status: New
** Changed in: ufw
Status: New => Triaged
** Changed in: ufw
Importance: Undecided => Medium
--
@Ivan, we are going to fix snapd for the excessive memory usage.
AppArmor upstream already uses expr-simplify by default and newer
release of Ubuntu use parser.conf to set -O no-expr-simplify so users
can manage the setting like any other conffile.
--
You received this bug notification because
** Changed in: pulseaudio (Ubuntu Xenial)
Status: In Progress => Triaged
** Changed in: pulseaudio (Ubuntu Bionic)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
** 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
** 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
Attaching test-snapd-pulseaudio and test-snapd-audio-record snaps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1781428
Title:
please enable snap mediation support
** 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
** Attachment added: "test-snapd-audio-record_1_amd64.snap"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+attachment/5292539/+files/test-snapd-audio-record_1_amd64.snap
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
+
+ # Original summary: pulseaudio built with --enable-snappy but 'Enable
+ Snappy support: no'
+
+ # Original description
+
From https://launchpadlibrarian.net/377100864/buildlog_ubuntu-cosmic-
amd64.pulseaudio_1%3A12.0-1ubuntu1_BUILDING.txt.gz:
...
This still seems to be a problem on Ubuntu 19.04. Ie, if I do:
$ sudo systemctl status systemd-rfkill
● systemd-rfkill.service - Load/Save RF Kill Switch Status
Loaded: loaded (/lib/systemd/system/systemd-rfkill.service; static; vendor
preset:
...
$ rfkill block bluetooth
$ rfkill
ID TYPE
Retriaging these down to Medium. People worked around this in different
ways and High was obviously inflated since it isn't fixed yet (I just
verified with 5.0.0-25.26-generic and apparmor 2.13.2-9ubuntu6.1).
** Changed in: apparmor
Importance: High => Medium
** Changed in: apparmor (Ubuntu)
This was fixed in 2.13.3-5ubuntu1 in Ubunt 19.10
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
@Rex and @Shih-Yuan, I believe Chris is planning to push this through
-security in his morning.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression:
> Please reject the packages that are currently in the unapproved queue.
Done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from
FYI, this broke me as well. I have an 18.04 multi-nic system that went
through several upgrades and was relying on /etc/udev/rules.d/70
-persistent-net.rules to give me predictable eth* names where each eth*
name was used as part of a bridge. The recent change regressed this
since non-existent
This should just all happen automatically in ufw based on bug feedback,
so marking ufw as "Won't Fix" instead of "Fix Released" since nothing
was needed in ufw (could've used Invalid, but that seemed worse than the
other two...)
** Changed in: ufw (Ubuntu)
Status: Triaged => Won't Fix
--
** Changed in: ufw (Ubuntu)
Status: New => Triaged
** Changed in: ufw (Ubuntu)
Importance: Undecided => Medium
** Changed in: ufw (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Tou
Can you perform the following:
$ mkdir /tmp/ufw
$ sudo ufw show raw > /tmp/ufw/raw
$ sudo tar -zcvf /tmp/1833719.tar.gz /tmp/ufw /etc/default/ufw /etc/ufw /lib/ufw
then attach to this bug /tmp/1833719.tar.gz?
** Changed in: ufw (Ubuntu)
Status: Expired => Incomplete
--
You received
Indeed, that is exactly what
https://git.netfilter.org/iptables/commit/?id=e5cab728c40be88c541f68e4601d39178c36111f
did. Are you saying there are other cases where a similar commit is
needed? IMO, those should be patched before 1.8.3 goes into eoan. Unless
I am missing something, iptables is
It seems like iptables going into a busy loop as non-root is also a bug
that should be fixed? At the very least, iptables should bail prior to
that condition saying that root is needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks for chasing this down! It seems clear that while the ufw
autopkgtest found the issue, the bug is not in ufw.
** 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
Public bug reported:
snapd needs the ability to call 'groupdel --extrausers foo' to clean up
after itself, but --extrausers is currently unsupported.
** Affects: snapd
Importance: Undecided
Assignee: Michael Vogt (mvo)
Status: New
** Affects: shadow (Ubuntu)
Importance:
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Medium
** Changed in: apparmor (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
This looks to be a local system issue with python3-minimal being removed
and then the prerm scripts from various programs failing due to
debhelper scripts that the package use can't find the required binaries.
Removing python3.6-minimal (3.6.8-1~16.04.york1) ...
Unlinking and removing bytecode
FYI, I tested this and 2.13.2-9ubuntu6.1 fixes this bug.
I also executed
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor (sans dbus
optional bits) and everything passed.
Lastly, I wanted to double check the performance impact of no-expr-
simplify on amd64 especially as it pertains to
Thank you for using ufw and filing a bug. Please keep in mind that the
firewall is sensitive to rule order. What is the output of 'sudo ufw
show numbered'?
** Changed in: ufw (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
Ubuntu 14.04 LTS is now out of standard support and evince is not
included in ESM.
** Changed in: evince (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Description changed:
+ [Impact]
+
+ * AppArmor 2.13 unconditionally invalidates its cache when parser options
are specified. To decrease compile times for ARM systems, -O no-expr-simplify
has been used in Ubuntu for click and snap policy for many years, but was
temporarily disabled during
** Changed in: apparmor
Status: In Progress => Fix Released
** Changed in: apparmor (Ubuntu Disco)
Status: Triaged => In Progress
** Changed in: apparmor
Assignee: (unassigned) => John Johansen (jjohansen)
--
You received this bug notification because you are a member of
** Changed in: apparmor (Ubuntu Eoan)
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/1820068
Title:
specifying -O
riaged
** Also affects: apparmor (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu Eoan)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: apparmor (Ubuntu Disco)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Description changed:
With 2.13.2 and the most recent testsuite patches from the 2.13 branch,
I find that the cache works correctly when no options are specified. Eg
# setup
$ mkdir -p /tmp/aa/cache /tmp/aa/profiles
$ cp /etc/apparmor.d/sbin.dhclient /tmp/aa/profiles/
# no
FYI, please note that seccomp 2.4.1 was pushed to bionic in
https://usn.ubuntu.com/4001-1/ on 2019/05/30. It shouldn't affect this
bug report AFAICT because while the 2.4.1 Ubuntu packaging drops these
patches, the upstream commits for lp-1815415-arch-update-syscalls-for-
Linux-4.9.patch and
This could be argued as Won't Fix since trusty is out of standard
support, but it did, in the end, receive an upgrade in trusty esm, so
marking Fix Released.
** Changed in: libseccomp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
This was fixed in upstream 2.3.2 which was fixed in cosmic. As of
https://usn.ubuntu.com/4001-1/ pulling back 2.4.1, this is now fixed
everywhere.
** Changed in: libseccomp (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
libseccomp was updated in trusty ESM here:
https://usn.ubuntu.com/4001-2/
--
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/1586496
Title:
Upgrade libseccomp library in
FYI, libseccomp is now published: https://usn.ubuntu.com/4001-1/
--
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/1830859
Title:
new libseccomp 2.4 (in proposed) makes
@Ian - how did you generate this profile? Is this something that snapd
generated (it doesn't look like typical snap-update-ns profiles...)? If
it did, can you attach the snap.yaml (this seems like atypical usage of
the layouts feature)?
--
You received this bug notification because you are a
** 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/1826429
Title:
package apparmor 2.13.2-9ubuntu6 failed to
I'm also seeing this behavior in gnome-shell on disco.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
"I guess the question is: Shouldn't we have a python-apport abstraction
that apps (or local admin) can include to make debugging work under
apparmor? It should probably live in apport, I guess, so apport can
define which files it needs."
Perhaps an abstraction makes sense to optionally add it in
I might also mention on IRC the exact type of thing why we've had these
rules in the profile that ship them:
[119698.000187] audit: type=1400 audit(1555405334.985:222):
apparmor="DENIED" operation="exec" profile="/usr/sbin/kopano-search"
name="/usr/bin/x86_64-linux-gnu-gcc-8" pid=15647
Traditionally we have actually put these accesses in the packages that
ship the profile, like Marc said, because profilers may not want the
profile to automatically have everything apport requires. These accesses
should *not* be in the python abstraction because the accesses have
nothing to do
Uploaded 2.13.2-9ubuntu6 with the SFS_MOUNTPOINT change.
--
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/1824812
Title:
apparmor does not start in Disco LXD containers
Since the apparmor SFS_MOUNTPOINT change is small, I'll prepare an
upload for that immediately. We may need another parser update for the
other issue.
** Changed in: apparmor (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
The following will reproduce the issue in a disco VM with disco LXD
container:
Initial setup:
1. have an up to date disco vm
$ cat /proc/version_signature
Ubuntu 5.0.0-11.12-generic 5.0.6
2. sudo snap install lxd
3. sudo adduser `id -un` lxd
4. newgrp lxd
5. sudo lxd init # use defaults
6. .
There are two bugs that are causing trouble for apparmor policy in LXD
containers:
1. the rc.apparmor.functions bug (easy fix: define SFS_MOUNTPOINT at the right
time
2. there is some sort of an interaction with the 5.0.0 kernel that is causing
problems
I'll give complete instructions on how
** Summary changed:
- apparmor no more starting in Disco LXD containers
+ apparmor does not start in Disco LXD containers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
This is due to a bug in upstream parser/rc.apparmor.functions because
SFS_MOUNTPOINT is only set after is_apparmor_loaded() is called, but
is_container_with_internal_policy() doesn't call it.
/lib/apparmor/apparmor.systemd calls is_container_with_internal_policy()
prior to apparmor_start() and it
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Changed in: libvirt (Ubuntu)
Status: New => Invalid
** Changed in: apparmor (Ubuntu)
Status: New => Triaged
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: apparmor (Ubuntu)
Importance: Undecided => H
To be clear, when I installed linux-modules-extra-5.0.0-8-generic, I no
longer saw this error message. Of course, it might not strictly be a
duplicate, but I'll let the kernel team figure that out.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
FYI, I saw this when looking at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862. In the
other bug, the reporter say a different error message, but I saw
'iptables v1.6.1: can't initialize iptables table `filter': Memory
allocation problem'. If those in this bug do not have
I can confirm that without linux-modules-extra-*, iptables is broken.
Reduced test case:
$ sudo iptables -L -n
iptables: No chain/target/match by that name.
Full test case:
$ sudo /usr/share/ufw/check-requirements -f
...
ERROR: could not create 'ufw-check-requirements'. Aborting
FAIL: check your
Marking the ufw task as Invalid. The kernel doesn't have what is needed
to run iptables.
** Changed in: ufw (Ubuntu)
Status: New => Invalid
** Changed in: ufw (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) => (unassigned)
--
You received this bug notification becau
"I can only think this is something cloud-image specific."
Can you provide the requested information in the earlier comments?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Another thing that might be useful is attaching a tarball of /lib/ufw,
/etc/ufw, and /etc/default/ufw.
--
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/1823862
Title:
disco:
FYI, I also tried the above with setting /etc/default/ufw to have
IPV6=no and everything works fine (and the v6 rules are not added).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
You said that the swift charm is disabling ipv6 in certain situations.
Is it updating /etc/default/ufw? Is it disabling it elsewhere? In the
failing instance, before trying to setup swift or run ufw or anything,
what is the output of 'sudo /usr/share/ufw/check-requirements'?
--
You received this
The usefulness of the policy aside (it is configured wide open), I still
can't reproduce with http://cdimage.ubuntu.com/ubuntu-
server/daily/current/disco-server-amd64.iso that I just downloaded:
$ sudo ufw default allow incoming
Default incoming policy changed to 'allow'
(be sure to update your
t; Incomplete
** Changed in: ufw (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 ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1823862
Title:
disco:
I've verified this on cosmic using a combination of test-ufw.py from QRT
(which in addition to various smoke/etc tests, runs all the tests in the
testsuite, including root/iptables tests):
ufw:
Installed: 0.36-0ubuntu0.18.10.1
Candidate: 0.36-0ubuntu0.18.10.1
Version table:
***
I've verified this on bionic using a combination of test-ufw.py from QRT
(which in addition to various smoke/etc tests, runs all the tests in the
testsuite, including root/iptables tests):
ufw:
Installed: 0.36-0ubuntu0.18.04.1
Candidate: 0.36-0ubuntu0.18.04.1
Version table:
***
Tested this is fixed in cosmic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.10.1
Candidate: 0.36-0ubuntu0.18.10.1
Version table:
*** 0.36-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64
Packages
500
Verified this is fixed in bionic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.04.1
Candidate: 0.36-0ubuntu0.18.04.1
Version table:
*** 0.36-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
500
Verified this is fixed in bionic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.04.1
Candidate: 0.36-0ubuntu0.18.04.1
Version table:
*** 0.36-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
500
Tested this is fixed in cosmic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.10.1
Candidate: 0.36-0ubuntu0.18.10.1
Version table:
*** 0.36-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64
Packages
500
Tested this is fixed in cosmic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.10.1
Candidate: 0.36-0ubuntu0.18.10.1
Version table:
*** 0.36-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64
Packages
500
Verified this is fixed in bionic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.04.1
Candidate: 0.36-0ubuntu0.18.04.1
Version table:
*** 0.36-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
500
Verified this is fixed in bionic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.04.1
Candidate: 0.36-0ubuntu0.18.04.1
Version table:
*** 0.36-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
500
Verified this is fixed in bionic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.04.1
Candidate: 0.36-0ubuntu0.18.04.1
Version table:
*** 0.36-0ubuntu0.18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
500
Tested this is fixed in cosmic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.10.1
Candidate: 0.36-0ubuntu0.18.10.1
Version table:
*** 0.36-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64
Packages
500
Tested this is fixed in cosmic:
$ apt-cache policy ufw
ufw:
Installed: 0.36-0ubuntu0.18.10.1
Candidate: 0.36-0ubuntu0.18.10.1
Version table:
*** 0.36-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64
Packages
500
201 - 300 of 1810 matches
Mail list logo
