[Group.of.nepali.translators] [Bug 1384532] Re: Unable to set AppArmor profile [...] no such file or directory
Hi, sorry for chiming in so late, but I haven't seen this issue before - the last update changed that. Special chars as reported in comment #26 and comment #15 are an issue, but most of them are fixed or at a better error message now. First of all since Ubuntu 17.10 (~=UCA-Pike) all files in generated rules are in quotes which formerly they were not - that allows for some chars like spaces. Further some other chars are just plain forbidden and would break the rule - these are mostly apparmor wilcards so these are now rejected since v3.10.0 by a150b86c instead of later failing when loading the profile. That said it is hard for me to track details of the old issue, but with a recent Ubuntu this should be all fixed. With space a rule will now look as: "/var/lib/uvtool/libvirt/images/a space does not hurt.qcow" rwk, and work just fine. But the actual issue - at least with tolerable special chars is fixed in the latter releases. And the apparmor wildcards do not randomly fail, or work or be a security issue - instead they always fail now. I have to admit the message is still the old misleading one in the remaining failing cases. I spawned bug 1767934 for this - but at low prio. Per above I'd set the bug fix releases at least for the latter releases. Given the long time this bug slumbers before a person is hit by it again and the fact that a simple file rename gets you around makes me not think of SRUs for this atm. So I'll set won't fix for pre-Artful, but hey - discussions welcome. ** Changed in: libvirt (Ubuntu) Status: Confirmed => Fix Released ** Also affects: libvirt (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Bionic) Importance: High Status: Fix Released ** Also affects: libvirt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Artful) Status: New => Fix Released ** Changed in: libvirt (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: libvirt (Ubuntu Bionic) Importance: High => Medium ** Changed in: libvirt (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: libvirt (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1384532 Title: Unable to set AppArmor profile [...] no such file or directory Status in libvirt package in Ubuntu: Fix Released Status in libvirt source package in Xenial: Won't Fix Status in libvirt source package in Artful: Fix Released Status in libvirt source package in Bionic: Fix Released Bug description: = Bugs are not infrequently reported along the lines of Unable to set Apparmor Profile for [emulator]: No such file or directory It is frequently (always?) the result of some value (a cdrom or disk file) which has spaces of odd characters which mess up virt-aa-helper or libvirt itself. We should attempt to detect this early on. Perhaps we can use a qemu hook, or add a check in virt-aa-helper. = /usr/bin/kvm-spice is a soft-link to /usr/bin/kvm in /etc/apparmor.d/abstractions/libvirt-qemu there is no line for kvm- spice. This leads rise to the error: libvirt: error : unable to set AppArmor profile 'libvirt-224075ba-a31a-48e9-98fe-337146e9f4f1' for '/usr/bin/kvm-spice': No such file or directory when using e.g. OpenStack $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 $ dpkg -l|grep libvirt-bin ii libvirt-bin 1.2.8-0ubuntu11 amd64programs for the libvirt library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics
The original xenial may not be affected (kernel 4.4), but xenial users do have the option of a HWE kernel, which would be affected... https://launchpad.net/ubuntu/+source/linux-hwe ** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Invalid ** No longer affects: linux-hwe (Ubuntu Artful) ** No longer affects: linux-hwe (Ubuntu Bionic) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1749420 Title: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-hwe source package in Xenial: New Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] Color dithering not working correctly because the graphics driver assumes the panel support 8bpc, but the panel only supports 6bpc. [Test] User reports the issue start appearing from v4.8-rc2. The issue is fixed with the patch. [Fix] Add a quirk to tell DRM that this panel only supports 6bpc. [Regression Potential] Low. This fix matches a very specific panel. === Original Bug Report === - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ystein 1344 F pulseaudio /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmeric
[Group.of.nepali.translators] [Bug 1767833] Re: [SRU] 2.32.6
** Also affects: snapd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1767833 Title: [SRU] 2.32.6 Status in snapd package in Ubuntu: New Status in snapd source package in Trusty: New Status in snapd source package in Xenial: New Status in snapd source package in Artful: New Status in snapd source package in Bionic: New Bug description: This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.32.6/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.32.6 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The travis logs for 2.32.6 can be found here: https://travis- ci.org/snapcore/snapd/branches We currently have no autopkgtest logs before snapd hits -proposed because we got asked to disable our autopkgtest integration as it was using too many resources from the autopkgtest infrastructure. The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767833/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
