From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110862] Dual-monitors invalid state after turning on
Date: Wed, 12 Jun 2019 09:36:28 +0000 [thread overview]
Message-ID: <bug-110862-502-Q1UNns7qpX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110862-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1063 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110862
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTOURBUG
--- Comment #8 from Michel Dänzer <michel@daenzer.net> ---
The xrandr output is probably different in the bad case as well, isn't it?
>From the bad case Xorg log file:
[421376.800] (II) AMDGPU(0): Allocate new frame buffer 2160x738
This means Xorg calls into the driver to resize the desktop to 2160x738 (which
explains why that area is OK, whereas the remaining area has undefined
contents). This is most likely in turn due to a client (probably some component
of the desktop environment you're using) requesting so via the RandR extension.
So it's either a bug in that or in the X server, not in the driver.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2562 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-06-12 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 19:19 [Bug 110862] Dual-monitors invalid state after turning on bugzilla-daemon
2019-06-11 9:02 ` bugzilla-daemon
2019-06-11 9:05 ` bugzilla-daemon
2019-06-11 18:04 ` bugzilla-daemon
2019-06-11 18:04 ` bugzilla-daemon
2019-06-11 18:05 ` bugzilla-daemon
2019-06-11 18:06 ` bugzilla-daemon
2019-06-11 18:07 ` bugzilla-daemon
2019-06-12 9:10 ` bugzilla-daemon
2019-06-12 9:36 ` bugzilla-daemon [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-110862-502-Q1UNns7qpX@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 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 NNTP newsgroup(s).