This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1
---------------
gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium
* Merge with Debian. Remaining change:
- Lower gnome-control-center dependency to 41
gnome-remote-desktop (42.1.1-2) unstable; urgency=high
* Don't automatically enable the systemd user service (LP: #1973028)
* Add postinst to remove the automatic enabling of the user service
* debian/control: Lower mutter dependency so that these fixes reach
Testing sooner
gnome-remote-desktop (42.1.1-1) unstable; urgency=medium
* New upstream release (LP: #1970662)
- Fixes black screen with virtio on qemu (LP: #1971195)
* Drop all patches: applied in new release
* Depend on libmutter instead of gnome-shell | budgie-desktop
- This is a more accurate dependency
* Require libmutter 42.1 for Nvidia fixes
* Depend on fuse3 (Closes: #998846) (LP: #1970411)
-- Jeremy Bicha <[email protected]> Thu, 12 May 2022 15:21:47 -0400
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1971195
Title:
gnome-remote-desktop leads to a session crash inside qemu with virtio-
vga
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in gnome-remote-desktop source package in Jammy:
Triaged
Bug description:
Steps to reproduce:
1. On a jammy host, create a jammy guest:
$ qemu-img create -f qcow2 vm.qcow2 50G
$ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device
virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO]
2. Install Ubuntu in that VM (minimal install), no problems are
expected yet.
3. After the installation is concluded and the VM reboots, try to
login using the Wayland session (it should be the default, no need to
select anything). It will fail and bring you back to the login screen
(apparently due to a gnome-shell crash; I don't think the details are
relevant to the problem here).
What is expected: that both the Wayland and X11 sessions work out-of-
the-box.
Workaround: remove gnome-remote-desktop, and the Wayland session will
work just fine in the conditions described above. This is why I'm
reporting this issue in gnome-remote-desktop instead of Wayland or
gnome-shell or qemu. I might be wrong though...
Extra information:
1. gnome-shell starts as expected if the X11 session is selected instead.
2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it
work in both the X11 and Wayland sessions:
$ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device
virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
