Increasing video memory appears to have fixed my problem.
My virtual screen size is 1920x1080 and in virt-manager's Video panel /
XML tab, vgamem was set to the default value of 16384. After increasing
it to 65536, I'm no longer seeing the freeze (though with only a few
minutes of testing, so
> Looks like with the latest update the problem is solved.
What packages got updated? Certainly not gnome-shell, mutter or mesa.
** No longer affects: mutter (Ubuntu)
** No longer affects: gnome-shell (Ubuntu)
** No longer affects: mesa (Ubuntu)
** Changed in: linux (Ubuntu)
Status:
Public bug reported:
I'm running a new installation of Ubuntu 22.04 Desktop on a Thinkpad
T450s (core i5-5200, 2 cores / 4 vCPUs, 12 GB memory). Using the virt-
manager GUI, I performed what I believe is a simple, plain-vanilla
installation of an Ubuntu 22.04 guest running under qemu/kvm with 2
All the same, perhaps vulkaninfo should issue a warning about vestigial
config if it can find a perfectly usable icd somewhere else! Presumably
it looks for the one supplied by Ubuntu.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
see, remnants of amdgpu-pro ;)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1959345
Title:
vulkaninfo reports error
To manage notifications about this bug go to:
Can't boot USB LiveCD of Kubuntu 20.04.4.
I've moved HDD from another PC with an almost fresh installation of 20.04.
ksplashqml crashes.
I'm trying to install Ubuntu 18.04.6. It won't load without pci=nomsi noapic
nolapic kernel args.
Next I'll try Kubuntu 16.04...
Also Dell Inspiron 1501
Looks like with the latest update the problem is solved.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971010
Title:
[vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in
As per the attachment, I can't really reproduce the problem in my bionic
chroot using the 390 driver from the archive, and Linux 4.15.0-178.187
from the CKT PPA.
** Attachment added: "390-non-failure.txt"
I'm surprised that:
(a) Xwayland is needed on startup. It shouldn't be started in a Wayland
session until a legacy app is launched.
(b) g_error ("Failed to start X Wayland: %s", error->message); is
fatal. It shouldn't be fatal because of (a), but indeed it apparently
still is in the latest
9 matches
Mail list logo
