Bug 390727 - Plasmashell does not cover 1440p monitor and behaves strangely
Summary: Plasmashell does not cover 1440p monitor and behaves strangely
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.12.1
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-19 11:02 UTC by Huan Truong
Modified: 2021-03-04 21:09 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
kde: Wayland+
kde: X11-


Attachments
KWin supportInformation (5.45 KB, text/plain)
2018-02-19 12:35 UTC, Huan Truong
Details
Wayland does not pick the right resolution - 1 (244.61 KB, image/png)
2018-04-10 06:33 UTC, Huan Truong
Details
Wayland does not pick the right resolution - 2 (231.30 KB, image/png)
2018-04-10 06:34 UTC, Huan Truong
Details
attachment-28334-0.html (1.58 KB, text/html)
2018-04-10 13:57 UTC, Huan Truong
Details
KInfoCenter (101.25 KB, image/png)
2018-04-15 12:30 UTC, Huan Truong
Details
Dump of env (2.87 KB, text/plain)
2018-04-15 12:30 UTC, Huan Truong
Details
Dump of weston-info (4.38 KB, text/plain)
2018-04-15 12:31 UTC, Huan Truong
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Huan Truong 2018-02-19 11:02:52 UTC
KDE Neon on Wayland has always been acting very strange with my 1440p monitor.

A brand new installation of plasma Wayland looks like this: https://imgur.com/a/wM3kW

When I start the session, the plasma desktop doesn't cover the whole 1440p screen, it seems like it only figures out a 1080 area to draw widgets. Everything outside of the 1080 area is black. Now if I start any program, the window will snap to the black area on the right and it never snaps to the "drawing area" on the left. If I maximize any window, it will maximize to the black area on the right. The black task switcher bar at the bottom of the screen is already maximized, it doesn't want to go lower or wider. 

I have tried both with Intel card and AMD RX 550 card, they produced the same result. It's a brand new installation of KDE Neon, and I can confirm it behaves the same way with Debian testing. It only happens with KDE on Wayland, KDE on X11 works fine. It's been 5-6 months since I observed this and it's still doing it today.
Comment 1 David Edmundson 2018-02-19 11:26:44 UTC
Please include output of:

qdbus org.kde.KWin /KWin supportInformation
Comment 2 Huan Truong 2018-02-19 12:35:48 UTC
Created attachment 110811 [details]
KWin supportInformation

KWin supportInformation is attached here.
Comment 3 Martin Flöser 2018-02-19 16:35:25 UTC
As we can see in the screenshot KWin covers the area correctly -> back to Plasma.
Comment 4 Huan Truong 2018-04-10 06:33:12 UTC
New information has come to light! I realized that this bug has something to do with the fact that wayland or kde actually sees one thing but does another with the 1440p screen I have. Please see attached screenshots. 

It totally sees that I have a 1440p screen (mode0) but it really picks the 1080p resolution (mode32). The disagreement between what the "real" resolution of the screen is is the culprit that the WM is behaving strangely.

If I fiddle with the resolution change in the system settings for a while (change it to another resolution and change it back to 1440p) KDE will crash and then take the 1440p resolution and behaves correctly.
Comment 5 Huan Truong 2018-04-10 06:33:57 UTC
Created attachment 111935 [details]
Wayland does not pick the right resolution - 1
Comment 6 Huan Truong 2018-04-10 06:34:15 UTC
Created attachment 111936 [details]
Wayland does not pick the right resolution - 2
Comment 7 Huan Truong 2018-04-10 06:36:00 UTC
THis is on KDE Neon userstable KDE plasma 5.12.4 I just downloaded today.
Comment 8 David Edmundson 2018-04-10 11:16:36 UTC
This is weird, the KWin information in comment #2

Screens
=======
Multi-Head: no
Active screen follows mouse:  no
Number of Screens: 1

Screen 0:
---------
Name: AUS HDMI-A-3-VA32AQ/H3LMAS000106
Geometry: 0,0,2560x1440
Scale: 1
Refresh Rate: 60

only has one screen
Comment 9 Huan Truong 2018-04-10 13:57:32 UTC
Created attachment 111938 [details]
attachment-28334-0.html

Sorry for the confusion. This time I tested on my laptop which has the
built-in screen and the 1440p screen connected via HDMI. Last time I tested
on the desktop which has only that 1440p screen connected via DP.

The bug is consistently reproducible on both the laptop and the desktop and
regardless of the connector type. If you want me to retry on the same
desktop, please let me know.



On Tue, Apr 10, 2018, 7:16 AM David Edmundson <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=390727
>
> --- Comment #8 from David Edmundson <kde@davidedmundson.co.uk> ---
> This is weird, the KWin information in comment #2
>
> Screens
> =======
> Multi-Head: no
> Active screen follows mouse:  no
> Number of Screens: 1
>
> Screen 0:
> ---------
> Name: AUS HDMI-A-3-VA32AQ/H3LMAS000106
> Geometry: 0,0,2560x1440
> Scale: 1
> Refresh Rate: 60
>
> only has one screen
>
> --
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.
Comment 10 David Edmundson 2018-04-11 10:16:59 UTC
I'm still stumped, sorry. Can I see three more things:

output of "env" in a terminal
your version of Qt (see kinfocenter)
output of "weston-info" (works fine on kwin, ignore the name)
Comment 11 Huan Truong 2018-04-15 12:30:00 UTC
Attached are the requested information. Thanks!

KDE Plasma v: 5.12.80
KDE Frameworks: 5.45.0
Qt v: 5.10.0
Kernel v: 4.13.0-38-generic
OS: 64bit
Comment 12 Huan Truong 2018-04-15 12:30:28 UTC
Created attachment 112042 [details]
KInfoCenter
Comment 13 Huan Truong 2018-04-15 12:30:49 UTC
Created attachment 112043 [details]
Dump of env
Comment 14 Huan Truong 2018-04-15 12:31:09 UTC
Created attachment 112044 [details]
Dump of weston-info
Comment 15 Christoph Feck 2018-05-10 14:32:51 UTC
Thanks for the update; changing status.
Comment 16 David Edmundson 2019-01-03 23:17:28 UTC
Output implies Qt is wrong. Please reopen if you still have an issue with Qt >=5.12