From: mikhail <mikhail.v.gavrilov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Olsak, Marek" <Marek.Olsak-5C7GfCeVMHo@public.gmane.org>,
"Daenzer, Michel" <Michel.Daenzer-5C7GfCeVMHo@public.gmane.org>
Cc: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
gpudriverdevsupport
<gpudriverdevsupport-5C7GfCeVMHo@public.gmane.org>
Subject: Re: LLVM 7.0 + Wayland = broken mouse control
Date: Tue, 30 Jan 2018 00:58:35 +0500 [thread overview]
Message-ID: <1517255915.3374.5.camel@gmail.com> (raw)
In-Reply-To: <BN4PR12MB08811DCADDC96DEDCAF61659F9E20-aH9FTdWx9BZt7gBpLs4TlwdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
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.
>
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next parent reply other threads:[~2018-01-29 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABXGCsMKWxAxDas=s2UxwydOYQ8TyEOCfR=0Mz0zGfgXxsnxcw@mail.gmail.com>
[not found] ` <188aeb48-741c-0658-32f5-b12d6389b10c@amd.com>
[not found] ` <BN4PR12MB08811DCADDC96DEDCAF61659F9E20@BN4PR12MB0881.namprd12.prod.outlook.com>
[not found] ` <BN4PR12MB08811DCADDC96DEDCAF61659F9E20-aH9FTdWx9BZt7gBpLs4TlwdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-01-29 19:58 ` mikhail [this message]
[not found] ` <1517255915.3374.5.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-29 22:10 ` LLVM 7.0 + Wayland = broken mouse control Marek Olšák
[not found] ` <CAAxE2A7FfYcLRdbrhJ_sWJ=JzKCjNrGO9bkELUUYJZemOAT2zw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-30 3:43 ` mikhail
2018-01-30 10:55 ` Michel Dänzer
[not found] ` <fa66db2b-0f75-e139-2fd9-ae42881d82df-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-01-30 16:27 ` mikhail
[not found] ` <1517329672.17945.4.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-30 16:52 ` Mike Lothian
[not found] ` <CAHbf0-ECicce-r8GbaPGWXxGB2RQr4HwSFkX1hFNjzST4Qf_jw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-30 17:40 ` mikhail
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1517255915.3374.5.camel@gmail.com \
--to=mikhail.v.gavrilov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Marek.Olsak-5C7GfCeVMHo@public.gmane.org \
--cc=Michel.Daenzer-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=gpudriverdevsupport-5C7GfCeVMHo@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.