>From the 1:6.1+dfsg-5 debian/rules file:
# gui modules. We move these here instead of using d/qemu-system-gui.install,
# b/c we install "all other" modules in qemu-system-common.install
# audio-pa.so pulls in X11 so we move it into -system-gui too
# hw-display-virtio-gpu-gl also pulls in X11,
This bug may be a regression from or otherwise related to the following
upstream commit for libvirt:
https://gitlab.com/libvirt/libvirt/-/commit/0c673246483cc4dbf0e6ecd6ea67ec0e2a5576af
..which was a fix for this libvrit bug caused by the above mentioned change in
QEMU at 6.1:
Package: python3-libvirt
Version: 7.0.0-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
qemu-system-common was upgraded to 6.1 from 5.2. This immediately broke
support for 3D acceleration
...@bugs.debian.org
Cc: David Gilmour <da...@gilmour.net>; r...@debian.org
Subject: Re: Bug#846173: libvirt-daemon: Fails to locate existing usb device
Hi,
thanks for the detailed investigation. I hit this bug when I upgraded my home
server. I have USB devices assigned to VMs based on the USB topolog
Paul,
On three separate machines, I experience the same problem. All of them are
"base" Stretch installs with xfce4 later installed via apt. Networking is
managed by systemd's networking.service. But all three are also kvm hosts,
and, as I mention in an earlier post for this bug, it appears
On Tue, 28 Feb 2017 15:07:39 +0100 Paul van Tilburg wrote:
> Hi!
>
> I have been struggling with the same issues. Because we want to offer a
> GNOME desktop, NetworkManager is installed. The way it configures the
> network might reveal an issue in xrdp itself.
>
> I have
Yes, I can confirm the problem occurs on 0.9.1-1.
I don't think it's a local configuration problem. Network and Network online
targets both are reached before the libvirtd.service starts. Indeed,
libvirtd.service declares that it must run after Network target is achieved.
But it then goes
Package: xrdp
Followup-For: Bug #840132
Dear Maintainer,
I have two systems on which xrdp fails to start at boot. On both
systems, subsequently running "systemctl start xrdp" always succeeds,
and if it is followed by "systemctl start xrdp-sesman", xrdp functions
normally and accepts sessions.
Package: libvirt-daemon
Version: 2.4.0-1+b1
Severity: important
Dear Maintainer,
I have a custom udev rule used to implement usb-hotplug support for the a
guest, whose name is dgw.
This is the contents of /etc/udev/rules.d/91-hotplug.rules:
---
ACTION=="add", \
SUBSYSTEM=="usb", \
9 matches
Mail list logo