[Bug 1607096] Re: lxc-container-default-with-mounting profile systemd permission denied
** Description changed: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) container and configure it to use the lxc-container-default-with- mounting. No further configuration needed. Start the container. You will find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" The container will appear start and you can attach, but its broken. Things like networking won't work. You cannot lxc-stop the container without -k. Starting the container in foreground mode leads to the following error. Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission Denied [!] Failed to mount API fileysystems, freezing. Freezing execution. I found defect https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 concerning Trusty. The issue seems similar but not specially calling out the aa profile. Also, I cannot actually recreate this problem in Trusty. + + (UPDATE: Forgot to mention I have 2 additional conf lines as follows) + lxc.cgroup.devices.allow = b 7:* rwm + lxc.cgroup.devices.allow = c 10:237 rwm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607096 Title: lxc-container-default-with-mounting profile systemd permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1607096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607096] Re: lxc-container-default-with-mounting profile systemd permission denied
** Description changed: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) container and configure it to use the lxc-container-default-with- mounting. No further configuration needed. Start the container. You will find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" - The container will appear to start and you can attach, but its broken. + The container will appear start and you can attach, but its broken. Things like networking won't work. You cannot lxc-stop the container without -k. Starting the container in foreground mode leads to the following error. Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission Denied [!] Failed to mount API fileysystems, freezing. Freezing execution. I found defect https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 concerning - Trusty. The issue seems very similiar but not specially calling out the - aa profile. Also, I cannot actually recreate this problem in Trusty. + Trusty. The issue seems similar but not specially calling out the aa + profile. Also, I cannot actually recreate this problem in Trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607096 Title: lxc-container-default-with-mounting profile systemd permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1607096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607096] [NEW] lxc-container-default-with-mounting profile systemd permission denied
Public bug reported: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) container and configure it to use the lxc-container-default-with- mounting. No further configuration needed. Start the container. You will find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" The container will appear to start and you can attach, but its broken. Things like networking won't work. You cannot lxc-stop the container without -k. Starting the container in foreground mode leads to the following error. Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission Denied [!] Failed to mount API fileysystems, freezing. Freezing execution. I found defect https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 concerning Trusty. The issue seems very similiar but not specially calling out the aa profile. Also, I cannot actually recreate this problem in Trusty. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) - container and configure it to use the lxc-container-with-mounting. No - further configuration needed. Start the container. You will find in - dmesg errors concerning problems mounting things in /sys/... + container and configure it to use the lxc-container-default-with- + mounting. No further configuration needed. Start the container. You will + find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" The container will appear start and you can attach, but its broken. Things like networking won't work. You cannot lxc-stop the container without -k. Starting the container in foreground mode leads to the following error. Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission Denied [!] Failed to mount API fileysystems, freezing. Freezing execution. I found defect https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 concerning Trusty. The issue seems very similiar but not specially calling out the aa profile. However, I cannot actually recreate this problem in Trusty. ** Description changed: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) container and configure it to use the lxc-container-default-with- mounting. No further configuration needed. Start the container. You will find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" The container will appear start and you can attach, but its broken. Things like networking won't work. You cannot lxc-stop the container without -k. Starting the container in foreground mode leads to the following error. Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission Denied [!] Failed to mount API fileysystems, freezing. Freezing execution. I found defect https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 concerning Trusty. The issue seems very similiar but not specially calling out the - aa profile. However, I cannot actually recreate this problem in Trusty. + aa profile. Also, I cannot actually recreate this problem in Trusty. ** Description changed: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) container and configure it to use the lxc-container-default-with- mounting. No further configuration needed. Start the container. You will find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" - The container will appear start and you can attach, but its broken. + The
[Bug 904962] Re: dash icon focused but window never appears
** Attachment added: Screenshot at 2011-12-15 15:35:35.png https://bugs.launchpad.net/bugs/904962/+attachment/2635115/+files/Screenshot%20at%202011-12-15%2015%3A35%3A35.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/904962 Title: dash icon focused but window never appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/904962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 904962] [NEW] dash icon focused but window never appears
Public bug reported: Neither clicking on the Dash icon or hitting super key brings up the Dash window. The icon does become focused and min/max/close still appears in the upper left. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.24.0-0ubuntu2b1 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Thu Dec 15 16:00:14 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] [1002:5b60] (prog-if 00 [VGA controller]) Subsystem: ATI Technologies Inc Device [1002:0602] Subsystem: ATI Technologies Inc Device [1002:0603] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Dell DXP051 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=d290cf0e-7539-48eb-bf7a-992982f035ee ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0FJ030 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/30/2006:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0FJ030:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell DXP051 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 oneiric regression-update running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/904962 Title: dash icon focused but window never appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/904962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 904962] Re: dash icon focused but window never appears
Also, did try a unity --reset which didn't change anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/904962 Title: dash icon focused but window never appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/904962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127101] Re: laptop hangs when switching video mode
Just an FYI, my Dell Inspiron 700m (w/ 855) still experiences the problem (when compiz is enabled) with the update posted yesterday the 18th http://www2.eng.cam.ac.uk/~pcjc2/ubuntu/xserver-xorg-video- intel_2.1.1-0ubuntu10~pcjc2_i386.deb installed. It sounded like the updated version might have worked for some, but not for me. For me I still suspend, resume, try to login, and I just see black, I have to reboot. -- laptop hangs when switching video mode https://bugs.launchpad.net/bugs/127101 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83623] Re: NetworkManager hangs with 100% cpu
I'm having this same problem on my Dell Inspiron 700m with the latest version of gutsy. -- NetworkManager hangs with 100% cpu https://bugs.launchpad.net/bugs/83623 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153816] Re: NetworkManager uses 95% CPU after changing eth0 to static address
Any relation to Bug #83623? I have essentially this problem but I've only noticed it after a suspend. I have the same messages in daemon.log. -- NetworkManager uses 95% CPU after changing eth0 to static address https://bugs.launchpad.net/bugs/153816 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136453] Re: [gutsy] resuming from suspend/hibernate broken
Am I alone here on my Dell Inspiron 700m? I'm having this problem after a clean install and update today. Recreation steps. 1) suspend 2) resume 3) log in 4) blank screen I checked the acpi prepare.sh and the 1 line correction is there. Adding the sleep kernel arg to menu.1st makes the problem worse (everything is blank, forced to reboot). Disabling compiz makes no difference. I tried switching from the intel driver to the i810 driver and suspend works now. ii acpi 0.09-3ubuntu1 ii acpi-support 0.103 ii acpid 1.0.4-5ubuntu8 xserver-xorg-video-intel2:2.1.1-0ubuntu7 -- [gutsy] resuming from suspend/hibernate broken https://bugs.launchpad.net/bugs/136453 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136453] Re: [gutsy] resuming from suspend/hibernate broken
The description in bug https://bugs.launchpad.net/ubuntu/+bug/127101 closely resembles my problem and it seems to be on going at this point. I'll assume that this defect isn't my problem since the things mentioned seem to have been fixed and I still have the issue. -- [gutsy] resuming from suspend/hibernate broken https://bugs.launchpad.net/bugs/136453 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
