On Mon, 2018-01-29 at 19:18 +0100, Marek Olšák wrote: > Please report this issue to the gnome-shell team. gnome-shell has a > bug in how they handle (or ignore) 10-bits-per-channel visuals. I already reported here: https://gitlab.gnome.org/GNOME/mutter/issues/2 > The workaround is to set the environment variable > "allow_rgb10_configs=false" for gnome-shell. I added environment variable as you said: # echo "allow_rgb10_configs=false" > /etc/profile.d/gnome-workaround.sh But it not helps workaround problem. Maybe we made a mistake in the diagnosis? On Wed, 2018-01-24 at 16:45 +0000, Olsak, Marek wrote: > Note that gnome-shell has a bug that if the driver supports 10bit > formats, incorrect drawing and wrong colors and/or corruption occur. > All drivers that say that they support 10bit formats won't work with > gnome-shell very well. > > My position on this issue is to keep Mesa as-is, leaving gnome-shell > broken, so that gnome-shell developers are alerted and fix their > code. If we react by removing 10bit support from drivers, the odds > are gnome-shell will never be fixed and drivers will never be able to > have 10bit support in them. > > Marek > > From: Daenzer, Michel > Sent: Wednesday, January 24, 2018 11:33:49 AM > To: Mikhail Gavrilov > Cc: gpudriverdevsupport > Subject: Re: LLVM 7.0 + Wayland = broken mouse control > > > On 2018-01-24 11:10 AM, Mikhail Gavrilov wrote: > > Hi. > > Anybody already tryied LLVM 7 and Wayland??? > > After LLVM is updated in repo > > https://copr.fedorainfracloud.org/coprs/che/mesa/ to 7.0.0- > 0.1.r322132 > > mouse hover are stop working on all controls. It means I unnable > > launch application by clicking on application icon also I unnable > drag > > and resize windows. And all controls are unclickable. But keyboard > > works fine. > > This sounds like the known gnome-shell/mutter bugs related to 10 > bits > per component colour formats. I.e. it's probably not directly related > to > LLVM but to changes in how Mesa exposes such formats to applications. > > > P.S. Please send this kind of inquiry to the amd-gfx mailing list > instead of this address. > >
