I forgot to link the upstream issue:
https://gitlab.gnome.org/GNOME/mutter/issues/204
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1778566
Title:
[radeon] Screen does not refresh till
I will report it there. But are you sure that is not a Wayland issue?
That something on the graphics loop can block the whole execution of the
program and be woken up by mouse movement sounds like a deep
architectural problem to me.
The graphics card is rare, it is integrated in a HP ProLiant
Public bug reported:
When Wayland is activated in GDM, nothing happens when selecting an
account with the keyboard or typing in the password. I have to type,
then wait, then move the mouse around for the characters to appears.
Because I wouldn't believe this report, I made a video of the
Public bug reported:
After upgrading from 12.04 to 14.04, direct rendering was not working.
glxinfo showed these errors:
onli@Fallout:~$ glxinfo
name of display: :0.0
libGL error: dlopen /usr/lib/dri/swrast_dri.so failed
(/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file
4 matches
Mail list logo