From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106529] Kernels 4.16+ confuses KDE wrt what the primary display is when waking up multiple displays
Date: Tue, 15 May 2018 15:00:35 +0000 [thread overview]
Message-ID: <bug-106529-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2459 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106529
Bug ID: 106529
Summary: Kernels 4.16+ confuses KDE wrt what the primary
display is when waking up multiple displays
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: mariusz.g.mazur@gmail.com
Created attachment 139577
--> https://bugs.freedesktop.org/attachment.cgi?id=139577&action=edit
ubuntu's 4.15 dmesg with amdgpu.dc_log=1
It appears that the display-handling code in 4.15+ (including 4.17-rc5) marks
any display not fully woken up as disconnected or something to that effect. So
when I have multiple monitors and they get woken up from sleep (doesn't matter
whether the computer was suspended or just idle for a long period), and my
primary display wakes up slower than the any of the other displays (and it
does), then for a few hundred ms KDE tries to change the primary display to the
one that first woke up (I'm guessing it thinks that's the only one available),
then changes its mind a bit later, when all displays wake up.
End result looks like crap and is not usable, since all my windows get
displaced. Here's how it looks like in practice:
Setup:
Radeon RX 560
Primary display: bottom right, displayport, on
Secondary display 1: left, hdmi, on
Secondary display 2: top right, dvi, off
Video of how it used to work, using 4.4.15:
https://www.youtube.com/watch?v=h7nMYbm5ZxU
Note how even though the left (secondary) display wakes up first, both
instantly display their proper desktops.
Video of how it works with ubuntu 18.04's default 4.15 kernel/4.16.7/4.17-rc5:
https://www.youtube.com/watch?v=VdVFNXPszSI
Note how when the left (secondary) display wakes up first, KDE decides that
this is probably the only display available, so tries to switch the primary
desktop to it, then a split second later the bottom right wakes up and KDE
knows *that* should be the primary according to the config, so it switches
back.
Attached is dmesg from ubuntu's 4.15 with dc_log=1. I put the computer to
sleep, then wake it up and get the behavior like in the video.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4065 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-05-15 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 15:00 bugzilla-daemon [this message]
2018-05-15 15:01 ` [Bug 106529] Kernels 4.16+ confuse KDE wrt what the primary display is when waking up multiple displays bugzilla-daemon
2018-05-15 15:19 ` bugzilla-daemon
2018-08-09 20:07 ` [Bug 106529] dc=1 kernels somehow trigger a disconnect of an lg ultrawide monitor during DP link training while attempting a wakeup bugzilla-daemon
2018-08-09 20:29 ` bugzilla-daemon
2018-08-15 14:43 ` bugzilla-daemon
2018-08-15 16:08 ` bugzilla-daemon
2018-08-15 17:29 ` bugzilla-daemon
2018-08-16 7:36 ` bugzilla-daemon
2019-11-19 8:38 ` bugzilla-daemon
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-106529-502@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).