This bug was fixed in the package linux - 4.4.0-9.24
---
linux (4.4.0-9.24) xenial; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1551319
* AppArmor logs denial for when the device path is ENOENT (LP: #1482943)
- SAUCE: apparmor: fix log of apparmor audit
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-xenial
--
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/1430546
Title:
apparmor kernel BUG kills firefox
Status in linux package in
The test kernel linked in comment #11 has been solid for me. I've not
hit this oops while running it. I accidentally rebooted into the latest
Vivid kernel and the kernel oopsed upon joining a Google Hangout.
--
You received this bug notification because you are a member of Kernel
Packages, which
There is a new test kernel for this issue at
http://people.canonical.com/~jj/lp1430546/
--
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/1430546
Title:
apparmor kernel BUG kills firefox
So this is failing because the task-cred does not equal the
task-real_cred during the update of the cred on the task
--
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/1430546
Title:
I've hit this bug in Vivid while attempting to join a Google Hangout.
Just before attempting to join the Hangout, I reloaded the Firefox
profile in complain mode while Firefox was already running.
** Attachment added: vivid-oops.txt
Can you please install the following test kernel and report whether it
fixes the issue
http://people.canonical.com/~jj/lp1430546/
--
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/1430546
Christopher,
Testing upstream kernels will not help with this issue as Ubuntu carries
a newer version of apparmor than is currently upstream. From the back
trace it is clear to me that the bug is in the newer code that ubuntu is
carrying. I am working on a patch and have a test kernel building.
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
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/1430546
Title:
apparmor kernel BUG kills firefox
Status in linux package
** Tags added: kernel-da-key
--
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/1430546
Title:
apparmor kernel BUG kills firefox
Status in linux package in Ubuntu:
Confirmed
Bug
Seth Arnold, did you mark this Confirmed because you already have a fix
lined up for this?
--
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/1430546
Title:
apparmor kernel BUG kills
** 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/1430546
Title:
apparmor kernel BUG kills firefox
Status in linux
** Attachment added: My /etc/apparmor.d/local/usr.bin.firefox
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430546/+attachment/4340496/+files/usr.bin.firefox
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: bios-outdated-4.10
** Tags added: regression-release
--
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/1430546
Title:
apparmor kernel BUG kills firefox
Status in linux
James Troup, thank you for reporting this and helping make Ubuntu
better. Could you please test the latest upstream kernel available from
the very top line at the top of the page (the release names are
irrelevant for testing, and please do not test the daily folder)
following
15 matches
Mail list logo
