http://bugzilla.suse.com/show_bug.cgi?id=1022727
http://bugzilla.suse.com/show_bug.cgi?id=1022727#c13
Rainer Krienke changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #13 from Rainer Krienke ---
After searching a while for this symptom I came across this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1174257#c6
The problem seems to be dri3 forwarding over ssh. In the bug report there is a
workaround. If I start yast2 on the remote side in the following way it works:
$ LIBGL_DRI3_DISABLE=1 /sbin/yast2 disk
Just running
$ /sbin/yast2 disk
does not work. Why this only happens when I connect to a SLES12SP2 system is
something I cannot explain. It happens with SLES12SP2 VMs as well as physical
SLES12SP2 systems. Running:
$ grep DRI /var/log/Xorg.0.log
2306.669] (II) glamor: EGL version 1.4 (DRI2):
[ 2306.785] (II) modeset(0): [DRI2] Setup complete
[ 2306.785] (II) modeset(0): [DRI2] DRI driver: i965
[ 2306.785] (II) modeset(0): [DRI2] VDPAU driver: i965
[ 2306.808] (II) GLX: Initialized DRI2 GL provider for screen
on my local 42.2 system, you see that my system is not using DRI3.
--
You are receiving this mail because:
You are on the CC list for the bug.