For me this was a bare metal bionic install on a home personal, multi-
purpose, intranet server (rsyslog, apache, bind9, etc). The message was
triggered 480 times in ~6 hours and 15 minutes before I downgraded. I
didn't notice other issues. I looked at the logs and couldn't see a
pattern of 'cut he
I started seeing this too after upgrading to this kernel (from
https://ubuntu.com/security/notices/USN-6081-1):
ii linux-image-generic4.15.0.211.194
ii linux-image-4.15.0-211-generic 4.15.0-211.222
$ cat /proc/version_signature
Ubuntu 4.15.0-211.222-generic 4.15.18
I started seeing the issues that Sergio mentioned lately as well. I
think this was caused by the recent automatic move from 5.8 to 5.11. I
had the oem kernel installed (20.04 install) but then apt recently moved
me to the hwe-5.8 kernel. More recently apt pulled in hwe-5.11 and I
believe that is wh
Thanks John! :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1898280
Title:
Please unrevert the apparmor audit rule filtering feature
Status in linux package in Ubuntu:
Fix Released
FYI, John refreshed the patchset to v20 and reenabled audit rule
filtering and submitted to https://lists.ubuntu.com/archives/kernel-
team/2020-October/113932.html. Since this is a significant change, it
will be considered for a stable release update (SRU) after groovy
release (to allow for peer re
After more discussion with John, while groovy does have a newer stacking
patchset, it doesn't have the latest patchset that resolves the audit
subsystem. Unfortunately, as of today, all of those patches haven't been
signed-off on yet so there might be future changes.
** Description changed:
Ubu
Public bug reported:
Ubuntu carried a patch to apparmor for audit rule filtering, but it was
reverted due to conflicts related to secids with earlier LSM stacking
patchsets. The upstream LSM stacking patchset is believed to resolve
these issues and groovy now carries the updated LSM stacking patch
FYI, John provided me a test kernel for 18.04 and it resolved the issue.
This will be the basis of the SRU.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890848
Title:
'ptrace trace' n
I cannot confirm this with the 5.8.0-12 kernel. Eg, with the 5.4 kernel
in groovy, things work fine:
$ cat /proc/version_signature
Ubuntu 5.4.0-42.46-generic 5.4.44
$ sudo modprobe iptable_filter
$ sudo modprobe ip6table_filter
$ lsmod|grep table_filter
ip6table_filter16384 0
ip6_tables
** Summary changed:
- No IPv4 iptable kernel module can be loaded
+ iptable_filter and ip6table_filter cannot be loaded with 5.8 kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18910
I spoke with John and he plans to SRU this. Marking as triaged and
assigning to him. Thanks John!
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu Bionic)
Status: C
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891020
Title:
No IPv4 iptable kernel module can be loaded
Status in linux pac
Thanks John! Is this something that we can get into the next SRU cycle?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890848
Title:
'ptrace trace' needed to readlink() /proc/*/ns/* fil
** Summary changed:
- 'ptrace trace' needed to readlink() /proc/*/ns/* files
+ 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Public bug reported:
Per 'man namespaces':
"Permission to dereference or read (readlink(2)) these symbolic links is
governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see
ptrace(2)."
This suggests that a 'ptrace read' rule should be sufficient to
readlink() /proc/*/ns/*, which is t
*** This bug is a duplicate of bug 1879690 ***
https://bugs.launchpad.net/bugs/1879690
Actually, this is 1879690 which is a bug in the Ubuntu kernel.
** Project changed: snapd => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** This bug has been marked a dupli
This entry:
* swap storms kills interactive use (LP: #1861359)
- SAUCE: mm/page_alloc.c: disable memory reclaim watermark boosting by
default
closed this bug, but per latest comments, that isn't sufficient to
address the issue. Putting back to Confirmed.
** Changed in: linux (Ubuntu Focal
Users seeing this issue should modify IPT_MODULES in /etc/defaults/ufw
to be empty. Ubuntu 20.04 will do this be default and future releases of
ufw will introduce rule syntax for working with helper rules.
--
You received this bug notification because you are a member of Kernel
Packages, which is
The linux task can be marked as Fix Released since
net/netfilter/nf_conntrack_helper has defaulted to 0 since 4.7.
** Changed in: ufw (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification becau
P_REVISION}/{,**}
rwl,
since the snap already has read/write access to these directories when
/system-data is not prepended. I've taken a todo to send up a PR for
this.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Triaged
** C
Using 5.4.0-17.21-generic, my laptop has 16G of ram. If I launch 3 vms
(xenial desktop (768M), bionic desktop (1.5G) and focal desktop (2.6G))
then load this page: https://people.canonical.com/~ubuntu-
security/oval/com.ubuntu.xenial.cve.oval.xml, at some point while the
page is loading, the deskto
I forgot to mention, I also have nvme.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861359
Title:
swap storms kills interactive use
Status in linux package in Ubuntu:
Confirmed
Bu
FYI, I decided to do this:
$ sudo swapoff -a && sudo swapon -a
$ free -h
totalusedfree shared buff/cache available
Mem: 15Gi 5.9Gi 4.8Gi 2.0Gi 4.8Gi 7.2Gi
Swap: 15Gi 348Mi15Gi
Even though I am no
Seth and I talked about this and I marked this as affects me. If it
helps, I saw this on eoan and focal doesn't make a difference (which
might suggest the change is between disco and eoan).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
This was fixed upstream in 61c27d8808f0589beb6a319cc04073e8bb32d860
** Changed in: apparmor
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824812
T
*** 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 =>
After discussing with Field, snapd, kernel and the security team, this
will break existing Ubuntu Core devices that use the 4.4 kernel and the
network-manager snap in the default channel (per reporter, the 1.10
channel is unaffected). Therefore, the 4.4 kernels snaps that include
this change (ie, 4
** 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 Kernel
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 lp-181
Uploaded 2.13.2-9ubuntu6 with the SFS_MOUNTPOINT change.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824812
Title:
apparmor does not start in Disco LXD containers
Status in AppArmor
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 Kernel
P
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. . /et
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 linux-module
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 Kernel
Packages, which is subscri
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 becaus
Are there additional steps that need to occur?
** Changed in: iptables (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1820114
Title:
iptables v
FYI, I cannot reproduce this with even less memory:
$ iptables --version
iptables v1.6.1
$ free
totalusedfree shared buff/cache available
Mem: 265712 114824 667441024 84144 36024
Swap: 0 0
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Ubuntu Security
Team (ubuntu-security)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Ubuntu Security
Team (ubuntu-security)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.
I too am seeing this after the most recent upgrade:
$ grep -cF 'sit: non-ECT' /var/log/syslog
2917
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772775
Title:
4.4.0-127.153 generates
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (unable to read library) on overlayf
This is fixed in xenial 2.3.1-2.1ubuntu2~16.04.1
** Changed in: libseccomp (Ubuntu Xenial)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567597
FYI, the following kernels are also affected (all 4.13 based):
* linux-azure
* linux-hwe
* linux-hwe-edge
* linux-oem
* linux-raspi2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1746463
Since this is going to be fixed in 'linux' and 'linux-gcp', adding tasks
for those.
** Changed in: apparmor (Ubuntu Artful)
Status: Won't Fix => Fix Committed
** Changed in: linux (Ubuntu Artful)
Status: Fix Committed => Confirmed
** Also affects: linux-gcp (Ubuntu)
Importance:
Add a snapd task so that when the https://launchpad.net/ubuntu/+source
/linux-gcp is Fix Released, snapd can re-enable the tests/main/lxd test
on GCE.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Fix Committ
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Won't Fix
** Changed in: qtmultimedia-opensource-src (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Marking the incomplete tasks as confirmed so the bot doesn't auto-close
the bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Artful)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ker
Since snapd is using this bug for its SRU blocker and we have bug
#1733700 that is the same issue, I'm going to use this bug as the snapd
one and for the apparmor one.
** Summary changed:
- utils don't understand «include "/where/ever"» (was: Potential regression
found with apparmor test on Xeni
@mvo - this is probably obvious, but if you used '#include' instead of
'include', it would side-step the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734038
Title:
utils don't
Marking as "Won't Fix" for the bluez deb -- the postinst is doing the
right thing, there just happens to be something installed outside of
dpkg/apt that is getting in the way.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you ar
Looking at the logs I see:
Sep 13 07:51:08 agda-HP-Pavilion-dv6500-Notebook-PC audit[1221]: AVC
apparmor="STATUS" operation="profile_replace" profile="unconfined"
name="snap.bluez.bluetoothctl" pid=1221 comm="apparmor_parser"
This indicates you have the bluez snap installed. This bug is about the
@Frode, I can yes, when I file them. I need to do a bit of work for
simple reproducers/etc/etc to file them. I've added an item to add a
comment to this bug when I do.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Closing the MAAS task as it the referenced bug is marked Fix Release. If
there are issues there still, please see my previous comment and look at
the code in that snap-- there are viable ways to use overlayfs with
chroot and an apparmor alias rule, or overlayfs with private mount,
chroot and pivot_
Actually, I marked the MAAS task as incomplete in case people want to
give feedback.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1408106
Title:
attach_disconnected not sufficient for
Ok, I spent quite a bit of time evaluating this and believe this bug can
be closed, but other bugs open.
In looking at this I created https://code.launchpad.net/~jdstrand/+git
/test-overlay (to build simply git clone, run 'snapcraft', install the
snap and then run 'test-overlay' for instructions o
4.4.0-65.86-generic fixes this issue on xenial.
** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
4.8.0-40.43-generic fixes this issue on yakkety.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1658219
Title:
flock not mediated by 'k'
Status in AppArmor:
In Progress
Status in linu
4.10.0-8.10-generic has the fix for this bug so marking the zesty task
as released.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: apparmor
Status: Triaged => In Progress
** Changed in: apparmor
Assignee: (unassigned) => John Johansen (jjohanse
FYI, this issue was hitting snapcrafters on Raspberry Pi3
(https://lists.ubuntu.com/archives/snapcraft/2017-February/003366.html).
Please also update the other reference kernels and snaps. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Confirmed this bug is fixed with 4.8.0-40.43-generic on yakkety.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Confirmed this bug is fixed with 4.4.0-65.86-generic on xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Changed in: apparmor
Status: New => In Progress
** Changed in: apparmor
Assignee: (unassigned) => John Johansen (jjohansen)
--
You
This is fixed with 4.10.0-8.10-generic. Marking zesty task as fixed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
Marking as 'confirmed' so the bot doesn't auto-close it.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636847
Title:
** Description changed:
This came up in snapd spread tests but can be reproduced with:
In an i386 up to date 16.04 VM:
1. in one terminal, run this:
- $ cat changehat_reproducer.sh
+ $ cat reproducer.sh
#!/bin/sh
set -e
sudo sysctl -w kernel.printk_ratelimit=0
sudo snap inst
Public bug reported:
This came up in snapd spread tests but can be reproduced with:
In an i386 up to date 16.04 VM:
1. in one terminal, run this:
$ cat changehat_reproducer.sh
#!/bin/sh
set -e
sudo sysctl -w kernel.printk_ratelimit=0
sudo snap install hello-world || true
count=0
while /bin/tru
FYI, this will likely cause tests in (at least) snap-confine to fail.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1626194
Title:
Seccomp actions are not audited in the 4.8 kernel
Sta
I found that the system sometimes suspends and resumes, seemingly ok,
but then there is a kernel trace when I try to reboot that halts the
reboot and need to hard reset on reboot. The trace is not logged.
With the kernel from xenial-updates (4.4.0.36) I found a reliable
reproducer:
1. boot
2. log
apport information
** Tags added: apport-collected
** Description changed:
I noticed this system failed to suspend properly and failed to resume.
Closed the lid, the fans kept going. Opened the lid and lights were
flashing indicating an error and had to hard reset. It had the following
i
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737710/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621899
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737709/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737712/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737711/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621899
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737706/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737700/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737707/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737702/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737704/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621899
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737705/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737708/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737703/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621899
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737701/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/16
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737699/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621899
Ti
Public bug reported:
I noticed this system failed to suspend properly and failed to resume.
Closed the lid, the fans kept going. Opened the lid and lights were
flashing indicating an error and had to hard reset. It had the following
in the logs:
Sep 9 07:43:19 ginny gnome-session[6351]: Tracebac
https://github.com/snapcore/snap-confine/pull/101
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584456
Title:
apparmor denial using ptmx char device
Status in Snappy Launcher:
In Pr
ged in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: snap-confine
Status: Confirmed => In Progress
** Changed in: snap-confine
Assignee: (unassigned) => Jamie Strandboge (jds
FYI, this is a requirement for snapd, but it was deprioritized in favor
of namespace stacking in support of LXD, upstreaming and other work in
support of snappy (eg, gsettings mediation). A lot of work was done to
support this, but the soonest it would be delivered given current
priorities is 17.04
Thank you for reporting a bug. The MAC in the log entry comes from the
kernel and contains several pieces of information: the src MAC, the dst
MAC and the TYPE. See http://logi.cc/en/2010/07/netfilter-log-format/
** Information type changed from Private Security to Public
** Package changed: ufw
This kernel has the bug:
$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605241152 SMP Tue May 24 16:01:12 UTC
2016
--
You received this bug notification because you are a member of Kernel
Packages, whic
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605241152 SMP Tue May 24 16:01:12 UTC
2016
Since the bug doesn't always show itself right away, I will want to use
the kerne
This kernel has the bug:
$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605201447 SMP Fri May 20 18:50:00 UTC
2016
--
You received this bug notification because you are a member of Kernel
Packages, whic
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605201447 SMP Fri May 20 18:50:00 UTC
2016
Since the bug doesn't always show itself right away, I will want to use
the kerne
This kernel has the bug:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160413 (Ubuntu 5.3.1-14ubuntu2) ) #201605181045 SMP Wed May 18 14:50:13 UTC
2016
--
You received this bug notification because you are a member of Kernel
Packages, which i
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160413 (Ubuntu 5.3.1-14ubuntu2) ) #201605181045 SMP Wed May 18 14:50:13 UTC
2016
Since the bug doesn't always show itself right away, I will want to use
the kernel f
This kernel does not seem to have the bug after using the system all
day:
$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605111621 SMP Wed May 11 20:26:24 UTC
2016
--
You received this bug notification
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605111621 SMP Wed May 11 20:26:24 UTC
2016
Since the bug doesn't always show itself right away, I will want to use
the kernel
This kernel has the bug:
$ cat /proc/version
Linux version 4.4.9-040409-generic (kernel@gomeisa) (gcc version 5.3.1 20160413
(Ubuntu 5.3.1-14ubuntu2) ) #201605041832 SMP Wed May 4 22:34:16 UTC 2016
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
I have booted into this kernel:
$ cat /proc/version
Linux version 4.4.9-040409-generic (kernel@gomeisa) (gcc version 5.3.1 20160413
(Ubuntu 5.3.1-14ubuntu2) ) #201605041832 SMP Wed May 4 22:34:16 UTC 2016
Since the bug doesn't always show itself right away, I will want to use
the kernel for at
Ah, that was fast. This kernel has the bug:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160311 (Ubuntu 5.3.1-11ubuntu1) ) #201603151533 SMP Tue Mar 15 19:37:15 UTC
2016
--
You received this bug notification because you are a member of Kernel
Apologies for the delay-- I needed our Ubuntu kernel for a number of
weeks and had to pause this bisection.
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160311 (Ubuntu 5.3.1-11ubuntu1) ) #201603151533 SMP Tue Ma
1 - 100 of 711 matches
Mail list logo
