I'm using qemu-bridge-helper already for a while. Since updating to
19.10 libvirtd suddenly refused to start my VMs. Turned out to be caused
by apparmor, I found these log messages:
audit: type=1400 audit(1580253669.262:100): apparmor="DENIED"
operation="file_inherit" profile="libvirtd//qemu_brid
I've got the same problem. We are using several closed source tools (for
FPGA building, code analysis, etc) which are 32-bit and e.g. call
getpwuid(). A few segfault because of the returned NULL pointer return
value caused by the missing libnss_winbind library.
--
You received this bug notificati
I also have a E6510 with these problems (on maverick). I tried the #185
kernel (just installed on maverick) and this solves all the problems. Is
there any chance this fixes will be backported to 10.10? Or is it safe
to run this kernel (which is meant for Natty)?
--
You received this bug notificat
Idem dito. Dell Inspiron 6400, screen stays off (black) after closing
and openening the lid, regardless of power management settings. Screen
is restored after a suspend-to-ram/resume cycle.
--
[i915gm] karmic 2.6.31-2 and -3 lid closing blacks screen until reboot on
thinkpad r52
https://bugs.lau
Same problem here: 3 services listed, only the last one has a name
("Audio service"). I messed a little bit with dbus-send:
$ dbus-send --system --print-reply --dest=org.bluez /org/bluez/service_audio
org.bluez.Service.GetName
method return sender=:1.110 -> dest=:1.134 reply_serial=2
string "A
