[Bug 1972075] Re: Blank screen when viewing GL-accelerated virtio screen on 22.04
I have submitted the patch upstream to the libvirt mailing list. I don't feel qualified to assert that giving the VM read access to those sysfs files is the right fix, but it did resolve the issue for me. I noticed that GNOME-Boxes bug too while troubleshooting this. I did not try the egl-headless suggestion at the end of the thread, but did attempt to set the env var "MESA_LOADER_DRIVER_OVERRIDE=i965", which still resulted in a blank display for me. It is unclear to me whether the "qemu_spice_gl_scanout_texture: failed to get fd for texture" message is specific to this issue, or if it would occur in a broad class of errors where the graphics fails to initialize. In my case, this is running on an i7-1165G7 Framework laptop with Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972075 Title: Blank screen when viewing GL-accelerated virtio screen on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1972075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972075] [NEW] Blank screen when viewing GL-accelerated virtio screen on 22.04
Public bug reported:
Also filed upstream:
https://gitlab.com/libvirt/libvirt/-/merge_requests/151
I recently upgraded from Ubuntu 21.10 to 22.04. I have an existing VM
with virtio video and gl-accelerated Spice display which previously
worked.
After the upgrade, virt-manager and virt-viewer display a blank screen.
In the qemu libvirt logs, I observe many repetitions of:
qemu_spice_gl_scanout_texture: failed to get fd for texture
dmesg contains these AppArmor errors:
[250001.100362] audit: type=1400 audit(1651958128.696:706): apparmor="DENIED"
operation="open" profile="libvirt-98a090a8-2fdf-463c-959b-810e5bc88b0d"
name="/sys/devices/pci:00/:00:02.0/revision" pid=132725
comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
[250001.100367] audit: type=1400 audit(1651958128.696:707): apparmor="DENIED"
operation="open" profile="libvirt-98a090a8-2fdf-463c-959b-810e5bc88b0d"
name="/sys/devices/pci:00/:00:02.0/config" pid=132725
comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
Modifying the AppArmor config for this VM to permit access to the
`revision` and `config` sysfs paths fixed this issue for me. The VM
display is visible and virgl is working. I was able to do so by adding
the following line:
"/sys/devices/**/{uevent,vendor,device,subsystem_vendor,subsystem_device,config,revision}"
r,
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Also filed upstream:
https://gitlab.com/libvirt/libvirt/-/merge_requests/151
I recently upgraded from Ubuntu 21.10 to 22.04. I have an existing VM
with virtio video and gl-accelerated Spice display which previously
worked.
After the upgrade, virt-manager and virt-viewer display a blank screen.
In the qemu libvirt logs, I observe many repetitions of:
- ```
qemu_spice_gl_scanout_texture: failed to get fd for texture
- ```
dmesg contains these AppArmor errors:
- ```
[250001.100362] audit: type=1400 audit(1651958128.696:706): apparmor="DENIED"
operation="open" profile="libvirt-98a090a8-2fdf-463c-959b-810e5bc88b0d"
name="/sys/devices/pci:00/:00:02.0/revision" pid=132725
comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
[250001.100367] audit: type=1400 audit(1651958128.696:707): apparmor="DENIED"
operation="open" profile="libvirt-98a090a8-2fdf-463c-959b-810e5bc88b0d"
name="/sys/devices/pci:00/:00:02.0/config" pid=132725
comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
- ```
Modifying the AppArmor config for this VM to permit access to the
`revision` and `config` sysfs paths fixed this issue for me. The VM
display is visible and virgl is working.
** Description changed:
** Description changed:
Also filed upstream:
https://gitlab.com/libvirt/libvirt/-/merge_requests/151
I recently upgraded from Ubuntu 21.10 to 22.04. I have an existing VM
with virtio video and gl-accelerated Spice display which previously
worked.
After the upgrade, virt-manager and virt-viewer display a blank screen.
In the qemu libvirt logs, I observe many repetitions of:
qemu_spice_gl_scanout_texture: failed to get fd for texture
dmesg contains these AppArmor errors:
[250001.100362] audit: type=1400 audit(1651958128.696:706): apparmor="DENIED"
operation="open" profile="libvirt-98a090a8-2fdf-463c-959b-810e5bc88b0d"
name="/sys/devices/pci:00/:00:02.0/revision" pid=132725
comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
[250001.100367] audit: type=1400 audit(1651958128.696:707): apparmor="DENIED"
operation="open" profile="libvirt-98a090a8-2fdf-463c-959b-810e5bc88b0d"
name="/sys/devices/pci:00/:00:02.0/config" pid=132725
comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
Modifying the AppArmor config for this VM to permit access to the
`revision` and `config` sysfs paths fixed this issue for me. The VM
- display is visible and virgl is working.
+ display is visible and virgl is working. I was able to do so by adding
+ the following line:
+
+
"/sys/devices/**/{uevent,vendor,device,subsystem_vendor,subsystem_device,config,revision}"
+ r,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972075
Title:
Blank screen when viewing GL-accelerated virtio screen on 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1972075/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted
Manually installing the libgphoto2 2.5.16 package in the bionic-proposed repo fixed this issue for me. https://launchpad.net/ubuntu/+source/libgphoto2/2.5.16-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729326 Title: Following upgrade to 17.10 Fugi X20 not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1729326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732858] Re: 2.5.14 broken for Fuji cameras (fixed upstream)
Manually upgrading to the 2.5.16-1 package in bionic-proposed [1] fixed this issue for me. [1] https://launchpad.net/ubuntu/+source/libgphoto2/2.5.16-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732858 Title: 2.5.14 broken for Fuji cameras (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1732858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732858] [NEW] 2.5.14 broken for Fuji cameras (fixed upstream)
Public bug reported: After upgrading to 17.10 gphoto2 fails to connect to my Fujifilm X-T2 camera, with the same errors as this user: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1729326 I believe the bug causing this was fixed upstream here (and included in later libgphoto2 versions): https://bugzilla.opensuse.org/show_bug.cgi?id=1048853 https://github.com/gphoto/libgphoto2/commit/472a9461b457b4d08ecf10a93bb7f1efdc2124c0 This bug is currently preventing me and other users from retrieving photos from Fujifilm cameras. Would it be possible to release an updated package with a more recent version, or applying the patch with the fix [1]? [1] https://build.opensuse.org/package/view_file/openSUSE:Factory/libgphoto2/libgphoto2 -fix-fuji.patch?rev=1a990f4295b7f4bbd99331eebd0752e0 ** Affects: libgphoto2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732858 Title: 2.5.14 broken for Fuji cameras (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1732858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted
It looks like this was fixed upstream: https://github.com/gphoto/libgphoto2/commit/472a9461b457b4d08ecf10a93bb7f1efdc2124c0 via https://bugzilla.opensuse.org/show_bug.cgi?id=1048853 https://build.opensuse.org/package/view_file/openSUSE:Factory/libgphoto2/libgphoto2-fix-fuji.patch?rev=1a990f4295b7f4bbd99331eebd0752e0 ** Bug watch added: bugzilla.opensuse.org/ #1048853 https://bugzilla.opensuse.org/show_bug.cgi?id=1048853 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729326 Title: Following upgrade to 17.10 Fugi X20 not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1729326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted
I'm experiencing the same error w/ a Fujifilm X-T2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729326 Title: Following upgrade to 17.10 Fugi X20 not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1729326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715811] Re: GDM crash loop Ubuntu 17.10 (Intel)
I ran into this upgrading from 17.04 to 17.10 on an X1 Carbon 3rd Gen (Intel HD Graphics 5500). Inspired by reading Mentis's comment. This fixed it for me: apt purge gdm gdm3 apt install gdm3 ubuntu-desktop (reinstalling ubuntu-desktop which got removed in the last step) Then running `systemctl restart gdm` got gdm3 to start successfully. Is it possible lingering config files from gdm (version 2?) are conflicting with gdm3 on some upgraded machines? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715811 Title: GDM crash loop Ubuntu 17.10 (Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1715811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634449] Re: Black flicker when leaving monitor
This appears to be a problem with the modesetting Xorg driver. After switching back to the intel driver (sudo cp /usr/share/doc/xserver-xorg- video-intel/xorg.conf /etc/X11/) I haven't seen this recur yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634449 Title: Black flicker when leaving monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634449] Re: Black flicker when leaving monitor
I am experiencing this issue as well on 16.10 on my X1 Carbon 3rd gen (Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz / HD Graphics 5500 (rev 09)). Tried mainline kernels 4.9.9, 4.9.10, and 4.10.0-997-drm-intel-next, and reproduced the issue on all. Also tried pinning libdrm2/linux-firmware /xserver-xorg-* to zesty versions, as well as installing intel- microcode, which made no difference. Xorg is running the modesetting driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634449 Title: Black flicker when leaving monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459756] Re: org.freedesktop.DBus.Python.dbus.exceptions.DBusException: com.ubuntu.USBCreator.Error.NotAuthorized
In my case, I was getting this error because I didn't have a PolicyKit authentication agent running. Launching `/usr/lib/policykit-1-gnome /polkit-gnome-authentication-agent-1` before running usb-creator-gtk fixed this issue for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459756 Title: org.freedesktop.DBus.Python.dbus.exceptions.DBusException: com.ubuntu.USBCreator.Error.NotAuthorized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1459756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
