Correction the bug number for the other bug is #1004606
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/453335
Title:
apparmor complains about write access to a readonly file
To manage notifications
I think this is actually causing a moderately serious regression with
snapshots.
If you look at the contents of an apparmor define for an example VM the
deny that silences the error here also prevents snapshot commits from
working and because the error is hidden makes this extra difficult to
debu
This bug was fixed in the package libvirt - 0.7.0-1ubuntu13.1
---
libvirt (0.7.0-1ubuntu13.1) karmic-proposed; urgency=low
* debian/patches/9093-lp460271.patch: require absolute path for dynamic
added files (LP: #460271)
* debian/patches/9094-lp453335.patch: suppress confusing
This bug was fixed in the package linux - 2.6.31-15.50
---
linux (2.6.31-15.50) karmic-proposed; urgency=low
[ Kees Cook ]
* SAUCE: Fix nx_enable reporting
- LP: #454285
linux (2.6.31-15.49) karmic-proposed; urgency=low
[ Benjamin Herrenschmidt ]
* [Upstream] (drop aft
Both the kernel and libvirt are ready to go to -updates, so I remove the
v-failed reminder tag now.
** Tags removed: verification-failed
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member
Thanks for the testing.
I added a verification-failed tag purely to avoid me accidentally
copying to -updates before the kernel. I'll revisit this when the kernel
is in, then it can go to -updates.
** Tags added: verification-done
** Tags removed: verification-needed
** Tags added: verification-
** Branch linked: lp:ubuntu/linux-mvl-dove
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
** Branch linked: lp:ubuntu/linux-fsl-imx51
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
With libvirt 0.7.0-1ubuntu13.1 and kernel 2.6.31-15.49-generic, I get
the following in /etc/apparmor.d/libvirt/libvirt-.files:
"/home/jamie/vms/isos/karmic/karmic-server-amd64.iso" r,
# don't audit writes to readonly media
deny "/home/jamie/vms/isos/karmic/karmic-server-amd64.iso" w,
Starti
** Changed in: libvirt (Ubuntu Karmic)
Status: In Progress => Fix Committed
** Changed in: libvirt (Ubuntu Lucid)
Milestone: karmic-updates => None
** Changed in: linux (Ubuntu Lucid)
Milestone: karmic-updates => None
** Changed in: linux (Ubuntu Lucid)
Status: In Progress
This bug was fixed in the package libvirt - 0.7.0-1ubuntu14
---
libvirt (0.7.0-1ubuntu14) lucid; urgency=low
* debian/patches/9093-lp460271.patch: require absolute path for dynamic
added files (LP: #460271)
* debian/patches/9094-lp453335.patch: suppress confusing and misleadin
I should also mention that libvirt should *MUST* be moved to karmic-
updates at the same time or after the kernel SRU for this bug, ie
2.6.31-15.49.
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you ar
SRU (libvirt)
Impact: confusing messages in kernel log. Told access to ISO is denied,
but it is correctly allowed.
Bug is addressed in Lucid adding a deny rule for the 'w' action, which
silences the message while still enforcing readonly
Patch is debian/patches/9094-lp453335.patch
See comment #
** Also affects: libvirt (Ubuntu Lucid)
Importance: Medium
Assignee: Jamie Strandboge (jdstrand)
Status: In Progress
** Also affects: linux (Ubuntu Lucid)
Importance: Medium
Assignee: John Johansen (jjohansen)
Status: In Progress
--
apparmor complains about write ac
Accepted linux into karmic-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
a
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Karmic)
Status: Triaged => In Progress
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a m
The latest version works well too:
http://kernel.ubuntu.com/~jj/linux-image-2.6.31-14-generic_2.6.31-14.49~jj_amd64.deb
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member of Ubuntu
Bugs, wh
This kernel allows me to have things like this in the profile and have it work
as expected:
"/home/jamie/vms/isos/karmic/karmic-server-amd64.iso" r,
# don't audit writes to readonly media
deny "/home/jamie/vms/isos/karmic/karmic-server-amd64.iso" w,
Ie, jj's kernel fixes this for me.
--
a
I have placed a test kernel at
http://kernel.ubuntu.com/~jj/linux-image-2.6.31-14-generic_2.6.31-14.48~jj_amd64.deb
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: apparmor
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
20 matches
Mail list logo