[Bug 1972075] Re: Blank screen when viewing GL-accelerated virtio screen on 22.04

2022-05-11 Thread Max Goodman
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

[Bug 1972075] [NEW] Blank screen when viewing GL-accelerated virtio screen on 22.04

2022-05-07 Thread Max Goodman
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

[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted

2017-11-16 Thread Max Goodman
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.

[Bug 1732858] Re: 2.5.14 broken for Fuji cameras (fixed upstream)

2017-11-16 Thread Max Goodman
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.

[Bug 1732858] [NEW] 2.5.14 broken for Fuji cameras (fixed upstream)

2017-11-16 Thread Max Goodman
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):

[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted

2017-11-16 Thread Max Goodman
It looks like this was fixed upstream: https://github.com/gphoto/libgphoto2/commit/472a9461b457b4d08ecf10a93bb7f1efdc2124c0 via https://bugzilla.opensuse.org/show_bug.cgi?id=1048853

[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted

2017-11-16 Thread Max Goodman
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 1715811] Re: GDM crash loop Ubuntu 17.10 (Intel)

2017-11-14 Thread Max Goodman
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

[Bug 1634449] Re: Black flicker when leaving monitor

2017-02-15 Thread Max Goodman
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

[Bug 1634449] Re: Black flicker when leaving monitor

2017-02-15 Thread Max Goodman
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

[Bug 1459756] Re: org.freedesktop.DBus.Python.dbus.exceptions.DBusException: com.ubuntu.USBCreator.Error.NotAuthorized

2015-12-27 Thread Max Goodman
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