Public bug reported:
There is a bug in mesa version 19.2.x where x>2, manifesting itself as
window contents in large windows on 4K display renders with an incorrect
vertical offset, making the desktop largely unusable for some customers.
The bug is fixed in latest 19.3 series and 20.0 rc series,
It looks like the logs you are posting are from a physical host running
the modesetting driver on top of an intel kms driver. That's AFAIK not a
VMware supported configuraion. Nevertheless you shouldn't see any
rendering corruption caused by the VMware drivers in the guest.
Could you post the vmwa
OK, So I tried to debug this on 17.04 with the mir demos.
What happens is that while the Mir server seems to run fine,
when the EGL mir clients import a surface from the mir server (using fds /
prime) they
typecast the XRGB surface from the mir server to an ARGB surface, which the
svga gallium d
Verified that with proposed updates in Ubuntu 12.04.5, the problem is
gone.
/Thomas
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1365490
Title:
ubuntu 12.04.5 broken on VM
Hi!
I now enabled proposed in Ubuntu 14.04 and did a full update:
dpkg -s libgl1-mesa-dri says
Version: 10.1.3-0ubuntu0.2
No sign of the bug symptoms. Everything working as expected.
I also enabled proposed in Ubuntu 12.04.5 and did a full update:
dpgk -s libgl1-mesa-dri-lts-trusty says
Version:
The problem is I can't verify the bug is fixed in trusty because it doesn't
show any obvious symptoms.
This is probably due to different stack ordering of local variables compared to
the trusty stack on precise.
The only way to verify the fix is in the trusty stack on precise where
the bug is ve
Chris, perhaps you can help me a bit by explaining here:
The buggy package in Ubuntu 12.04.5 that was on the installation iso and
that I rebuilt locally with the fix before filing the bug was called
mesa-lts-trusty. How does that relate to this package?
Thanks,
Thomas
On 10/01/2014 02:04 PM, Ch
[Impact]
A user might find Ubuntu 12.04.5 unusable on vmware because he would
face a black screen after logging in. Although there is a workaround
(disabling 3D) a user may have given up at that point.
Backporting will help the user run the distro after upgrading, so I
believe it's highly justifi
OK, so from within 14.10 things appear to work OK. XMir fires up as
well, so feel free to close this bug if desired.
Thanks,
Thomas
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bug
Sure, I'll try that, although I thought Ubuntu 14.04 had some sort of
"stable mir 7" environment shipped with it.
BTW is XMir still alive with 14.10?
/Thomas
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
htt
Public bug reported:
When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in the
following location:
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such
file or directory.
(gdb) bt
#0 pthr
Public bug reported:
When using unity / compiz on top of llvmpipe and switching resolution
from something lower to 1600x1200 (This is a virtual machine, so this
happens regularly), compiz crashes.
Description:Ubuntu 14.04.1 LTS
Release:14.04
libgl1-mesa-dri:
Installed: 10.1.3-0ubun
12 matches
Mail list logo