From: Stefan Kangas <stefan@marxist.se>
To: Bastian Beischer <bastian.beischer@gmail.com>
Cc: 38199@debbugs.gnu.org
Subject: bug#38199: 27.0.50; [Cairo] Display artifacts (small vertical colored bars)
Date: Tue, 25 Aug 2020 16:22:06 -0700 [thread overview]
Message-ID: <CADwFkm=AmAdEok31W7UuM-iaQxc-U+7tfGKZWPCkCkb=CfR9pw@mail.gmail.com> (raw)
In-Reply-To: <CAK9AuB90cWAHrrj7W=NF+waaWsf6pT0bO=TS44GbAvL+VbvxbQ@mail.gmail.com> (Bastian Beischer's message of "Sat, 23 Nov 2019 14:03:11 +0100")
tags 38199 + notabug
close 38199 28.1
thanks
Bastian Beischer <bastian.beischer@gmail.com> writes:
> On Fri, Nov 15, 2019 at 8:59 AM Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> > From: Bastian Beischer <bastian.beischer@gmail.com>
>> > Date: Thu, 14 Nov 2019 23:30:32 +0100
>> > Cc: 38199@debbugs.gnu.org
>> >
>> > > Did you try to disable "advanced" or "optimization" features of your
>> > > display driver software? Or upgrade it to a newer version? The
>> > > artifacts your screenshot shows don't look like something Emacs could
>> > > produce.
>> >
>> > You are right: It could well be a cairo library or driver issue. I am
>> > using the default optimized builds from the Arch Linux x86_64
>> > repository, which means:
>> >
>> > cairo: 1.17.2+17+g52a7c79fd-2
>> > Xorg: 1.20.5-4
>> > mesa: 19.2.3-2
>> > linux: 5.3.11.1-1
>> >
>> > My GPU is NVIDIA Geforce GTX 285 (nouveau kernel driver, combined with
>> > modesetting / glamor). Should I report a bug against cairo?
>>
>> Maybe; it could also be a bug in the NVIDIA drivers. So before
>> reporting a Cairo bug, I'd look at the settings of your video driver,
>> and if there are any "optimization" features there, try to disable
>> them.
>
> I have now confirmed the bug on a different PC with an Intel GPU. It
> persists when using modesetting and when using xf86-video-intel as
> drivers there. So I think it's unlikely that it is a bug in the
> driver.
>
> I will now open a cairo issue.
The above discussion indicates this is most likely a bug in cairo and
not in Emacs. I'm therefore closing this bug report.
If this conclusion is incorrect and this is still an issue, please reply
to this email (use "Reply to all" in your email client) and we can
reopen the bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2020-08-25 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 19:32 bug#38199: 27.0.50; [Cairo] Display artifacts (small vertical colored bars) Bastian Beischer
2019-11-14 13:30 ` Eli Zaretskii
2019-11-14 15:33 ` Dmitry Gutov
2019-11-14 22:30 ` Bastian Beischer
2019-11-15 7:59 ` Eli Zaretskii
2019-11-23 13:03 ` Bastian Beischer
2020-08-25 23:22 ` Stefan Kangas [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=AmAdEok31W7UuM-iaQxc-U+7tfGKZWPCkCkb=CfR9pw@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=38199@debbugs.gnu.org \
--cc=bastian.beischer@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).