Changed the target to be apparmor because the kernel panic is triggered
by apparmor.
** Package changed: linux (Ubuntu) => apparmor (Ubuntu)
** Also affects: apparmor
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seede
I added linux back due to the uncanny resemblance to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508737
and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586997
Thanks
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notifi
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Ignore the request to test the upstream kernel, for the moment.
In this case the apparmor code that is in the trace does not exist upstream.
Instead could you test the kernel in
http://people.canonical.com/~jj/lp1648143/
While listed as being for bug 1648143, it contains several fixes
includin
Actually, this bug was found with Ubuntu all-snap version. So I am not able to
try the kernel.deb. Could you tell me how to get the latest version of the
kernel snap for 16.04?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
sudo snap refresh
should refresh the kernel snap. However the suspected fix will not be in
any snap kernel, nor can I atm build you a kernel snap to test with.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubun
6 matches
Mail list logo