Bug 415871 - Maximize window on second monitor does not expand window to whole screen
Summary: Maximize window on second monitor does not expand window to whole screen
Status: RESOLVED DUPLICATE of bug 461142
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 5.19.5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-04 12:27 UTC by Alexander Radzishevsky
Modified: 2023-09-06 22:56 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot of screens with bug (894.90 KB, image/jpeg)
2020-01-04 12:27 UTC, Alexander Radzishevsky
Details
Screenshot of problem (1.53 MB, image/png)
2020-06-05 18:07 UTC, Trevor Allen
Details
Screenshot after I upgraded to 5.19 (989.32 KB, image/png)
2020-06-10 10:20 UTC, Tamás Gere
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Radzishevsky 2020-01-04 12:27:32 UTC
Created attachment 124893 [details]
Screenshot of screens with bug

SUMMARY
Windows on second screen having no task panel are not maximized: there is a gap below window. Height of the gap is of the same size as task panel height on first screen.
Windows can be manually (via mouse, for example) resized to whole screen though, only maximize button does not work properly.   
Note that there were no such a bug in Plasma 15.6

STEPS TO REPRODUCE
1. Connect second monitor (there should be no task panel on that second monitor)
2. Move any window to second monitor
3. Maximize window

OBSERVED RESULT
Window does not take whole monitor space. There is a gap below window and bottom of the screen. 

EXPECTED RESULT
Window must take whole screen

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Kubuntu 19.10
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION
Two 4K monitors setup. Scaling factor is 2.
Comment 1 Alexander Radzishevsky 2020-01-09 11:49:08 UTC
Additional information: I do not have this bug anymore on Plasma 5.17.5
Comment 2 Alexander Radzishevsky 2020-01-09 17:46:23 UTC
I would like to notify that this bug reproduced again. On 5.17.5. So I am reopening this
Comment 3 Trevor Allen 2020-06-05 07:55:24 UTC
Still a problem as of 06/05/2020
Comment 4 Alexander Radzishevsky 2020-06-05 08:27:21 UTC
Yes, just installed kubuntu 20.04 fresh and it is still there:

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-33-generic
OS Type: 64-bit
Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz
Memory: 62,7 GiB of RAM
Comment 5 Michail Vourlakos 2020-06-05 08:43:46 UTC
Works just fine in my Tumbleweed system
Comment 6 Trevor Allen 2020-06-05 18:07:05 UTC
Created attachment 129081 [details]
Screenshot of problem

Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.4.43-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 23.4 GiB of RAM
Comment 7 Tamás Gere 2020-06-10 10:20:37 UTC
Created attachment 129190 [details]
Screenshot after I upgraded to 5.19

Interestingly the problem appeared after I upgraded to 5.19. It wasn't the case before.

Operating System: KDE neon User Edition 5.19
KDE Plasma Version: 5.19.0
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.3.0-28-lowlatency
OS Type: 64-bit
Processors: 4 × Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
Memory: 20.0 GiB of RAM
Comment 8 Neil Moore 2020-06-11 15:59:47 UTC
This looks similar to the issue I reported in https://bugs.kde.org/show_bug.cgi?id=420263, but I don't see any pixel overlap in your screenshot.
Comment 9 Alexander Radzishevsky 2021-02-04 14:24:29 UTC
It is still there with newest Kubuntu:

Operating System: Kubuntu 20.10
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Kernel Version: 5.8.0-41-generic
OS Type: 64-bit
Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz
Memory: 62,7 GiB of RAM
Graphics Processor: Quadro M2000M/PCIe/SSE2
Comment 10 Michail Vourlakos 2021-02-04 16:28:45 UTC
(In reply to Alexander Radzishevsky from comment #9)
> It is still there with newest Kubuntu:
> 
> Operating System: Kubuntu 20.10
> KDE Plasma Version: 5.19.5
> KDE Frameworks Version: 5.74.0
> Qt Version: 5.14.2
> Kernel Version: 5.8.0-41-generic
> OS Type: 64-bit
> Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz
> Memory: 62,7 GiB of RAM
> Graphics Processor: Quadro M2000M/PCIe/SSE2

1. With git version under Tumbleweed I dont have that issue
2. What is your Latte version?
3. If you are using v0.9.11 this is not maintained any more
4. Are you using X11 or wayland?
5. Send your layout file please
Comment 11 Alexander Radzishevsky 2021-02-04 18:28:02 UTC
> 1. With git version under Tumbleweed I dont have that issue
here I have nothing to add...

> 2. What is your Latte version?
if you are talking about Latte Dock, I am not using it.

> 3. If you are using v0.9.11 this is not maintained any more
see p.2

> 4. Are you using X11 or wayland?
X11

> 5. Send your layout file please
Pardon, what is "layout file" ?
Comment 12 Michail Vourlakos 2021-02-04 18:39:48 UTC
Oh so sorry, dont bother, forget my comments I didnt notice that this was for Plasma.
Comment 13 Michail Vourlakos 2021-02-04 18:40:13 UTC
I faulty changed state previously
Comment 14 Méven Car 2021-10-05 13:34:22 UTC
Is it still occuring ?

Does using X or Wayland change the situation ?
Comment 15 tngTUDOR 2022-07-06 09:48:49 UTC
I can reproduce with:

Operating System: Fedora 36
KDE Plasma Version: plasma-desktop-5.25.2-1.fc36.x86_64
Qt Version: qt5-qtbase-5.15.3-3.fc36.x86_64
Kernel Version: 5.5.7-200.fc31.x86_64
OS Type: 64-bit
Processors: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
Memory: 16 GiB of RAM
Graphics Processor: 02:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2) + 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
Wayland: 1.20.0-4.fc36.x86_64
Comment 16 Andrew Shark 2023-09-06 22:56:27 UTC
*** This bug has been marked as a duplicate of bug 461142 ***