*** This bug is a duplicate of bug 1167622 ***
https://bugs.launchpad.net/bugs/1167622
** This bug has been marked a duplicate of bug 1167622
Cannot change EFI variables using efibootmgr (raring regression)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Same problem here on an AMD A4-5300 APU using the radeon driver.
Freezing particularly occurs when I scroll in firefox. Interestingly,
when using the chromium-browser instead, this problem occurs much less
frequently. As soon as the freeze occurs, unity does not respond to
mouse and keyboard input
With 3.8.0-12-generic, my computer with an ASRock FM2A75 Pro4-M
mainboard, which booted fine with 3.8.0-11-generic in UEFI mode, hangs
on boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1146868
In the meantime, I have erased the contents of my EFI parition and
reinstalled grub to it. Now, my computer boots fine again, also with
3.8.0-12-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since having updated to the latest linux image (linux-
image-3.8.0-6-generic_3.8.0-6.11_amd64.deb), which was rebased to kernel
version 3.8-rc7, a few days ago, I have not experienced any freezes of
unity. Even when using firefox and doing excessive scrolling, which was
very likely to cause
On saucy, with kernel 3.11.0-2-generic, I sometimes get the same error
message when having Radeon DPM enabled (radeon.dpm=1). Unity desktop
then freezes and after a few seconds, the screen turns black. However, I
can switch to the console and reboot. When leaving DPM disabled
(radeon,dpm=0), I
With libvirt 1.2.12-0ubuntu8 being installed, virsh still fails to start
an LXC operating system container, resulting in the following dmesg:
[ 126.832553] audit: type=1400 audit(1427571328.167:150): apparmor=DENIED
operation=open profile=/usr/lib/libvirt/virt-aa-helper
This is the XML (virsh -c lxc:/// dumpxml test):
domain type='lxc'
nametest/name
uuid9d578815-a1e9-4596-aef9-a70717574f0e/uuid
memory unit='KiB'1048576/memory
currentMemory unit='KiB'1048576/currentMemory
vcpu placement='static'2/vcpu
resource
partition/machine/partition
It seems as if /etc/apparmor.d/abstractions/libvirt-lxc is also missing
at least one necessary entry. In current Vivid,
$ virsh -c lxc:/// start test
fails, resulting in the following dmesg:
[ 2207.856469] audit: type=1400 audit(1427382800.914:235): apparmor=DENIED
operation=open
The container can be booted via lxc-start using the attached config.
The container can also be booted using libvirt-lxc as long as it is
configured to use /sbin/upstart as init.
However, when configured to boot on /bin/systemd, it still fails as
reported above.
Is anyone else experiencing this
Thank you for pointing this out.
Based on your reply, I decided to have the host system boot on
/bin/systemd and have the containers boot on /sbin/upstart. So far, this
works without problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorry, for an unknown reason, a wrong package was selected when I
submitted the bug. I think that the bug affects the Ubuntu standard
session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455809
Public bug reported:
Following situation:
- Ubuntu is configured use SSSD to permit login of LDAP users
- Automatic creation of home directories is switched on and confirmed to work
- LDAP users (as well as local users) can login to
* local console
* SSH console
* LXDE (via LightDM)
*
** Attachment added: Relevant section of auth.log
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1455809/+attachment/4398636/+files/auth.log
** Package changed: sddm (Ubuntu) = gnome-session (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Under vivid, a vivid container fails to boot with systemd, printing the
following error message in console:
Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied
systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK
+SYSVINIT +UTMP
Public bug reported:
Under vivid, a vivid container fails to boot with systemd, printing the
following error message in console:
Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied
systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK
+SYSVINIT +UTMP
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455809
Title:
[vivid] Ubuntu session crashes on LDAP login via SSSD
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1486000 ***
https://bugs.launchpad.net/bugs/1486000
** This bug has been marked a duplicate of bug 1486000
amule crashed with SIGABRT in wxVLogFatalError()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Using virt-manager and libvirtd, I added a VirtFS filesystem passthrough
to an existing qemu virtual machine also running Ubuntu.
The XML code generated by libvirt looks like this:
Inside the VM, I am able to mount the filesystem
** Tags removed: p9
** Tags added: 9p
** Summary changed:
- [xenial] No write access to VirtFS (p9) in qemu VM run by libvirt
+ [xenial] No write access to VirtFS (9p) in qemu VM run by libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Using virt-manager and libvirtd, I added a VirtFS filesystem passthrough
to an existing qemu virtual machine also running Ubuntu.
The XML code generated by libvirt looks like this:
Inside the VM, I am able to mount the filesystem
Public bug reported:
/usr/lib/apt-cacher-ng/distkill.pl is missing!
As mentioned here
https://www.unix-ag.uni-kl.de/~bloch/acng/html/maint.html#distkill
and also here
https://wiki.ubuntuusers.de/Lokale_Paketquellen/Apt-Cacher-ng/#Distkill
this script is needed to get rid of the DEB files of
Thanks again Eduard, for submitting the improvement proposal to the
project's todo list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635029
Title:
apt-cacher-ng in yakkety lacks distkill.pl
To
Thanks Eduard!
Based on your hint, I was able to figure out what needs to be done:
1. Open http://:3142/acng-report.html in the browser
2. Click "Start Scan and/or Expiration" button
3. Wait for the scan to finish
4. After the scan has finished, navigate to "Allocated disk space (Top 10, show
Public bug reported:
lxd-tools used to ship the fuidshift command which is useful for
shifting UIDs and GIDs of the container root filesystem in order to
convert privileged into unprivileged containers. lxd-tools is now a meta
package that will enforce that the lxd snap package is being
Public bug reported:
I used equivs in the past to build meta packages to ensure that certain
packages are installed on my systems. This always worked well.
With the Ubuntu 19.10, I am unable to build any meta package with equivs
even though the program does not report any error. Running
Hm, I just figured out that I missed the last really useful comment
because I did not get an e-mail about it.
Anyway, https://github.com/lxc/lxc/issues/3186 now explains in more
detail how to quickly build fuidshift from source.
Thank you, Stéphane!
** Bug watch added: LXC bug tracker #3186
27 matches
Mail list logo
