Bug 308853

Summary:	Dualhead: wrong upper bound on primary smaller monitor, if not positioned at 0,0
Product:	[Plasma] kwin	Reporter:	Georgios Varisteas <yorgos.v>
Component:	xrandr	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	tap3ahchina
Priority:	NOR	Keywords:	triaged
Version First Reported In:	4.9.2
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	dual monitor setup

Description Georgios Varisteas 2012-10-23 08:51:57 UTC

Hi,

I have a dual monitor setup with a laptop. My LVDS is 1366x768 and VGA at 1600x1200. When placed side by side, VGA: RightOf LVDS, they are aligned at the top. I do not want that so I align them at the bottom by setting positions to:
LVDS: absolute 0x432 (1200 - 768)
VGA: absolute 1367x0

When set that way, the smaller primary monitor LVDS, looses its proper upper bound. For example, maximized windows overflow the screen upwards even though I have panels on both sides. The panels are fine. The mouse also is not restricted traveling out of bounds.

I know that this can be solved by setting VGA as primary, I do not want that cause it messes up my panels when I move the laptop. 

The reason I want this setup is so that I can move between monitors from the lower parts of the larger monitor. Most frequently the mouse lays there and it's annoying every time to have to think to move it lower before going left.
Justin case you wonder

Reproducible: Always

Steps to Reproduce:
1. Get two monitors of different sizes
2. Set the smaller as primary
3. Place them side by side, aligned at the bottom
4. Try to maximize a window
Actual Results:  
The window overflows the screen upwards

Expected Results:  
The window should stay inbound of the desktop

This problem alone makes such configurations totally unusable

Comment 1 Thomas Lübking 2013-06-06 17:54:34 UTC

"works for me"

Is this still a problem?
In case:
- please  post the output of "xrandr -q" on that setup.
- does it also happen if you quit plasma (kquitapp plasma-desktop) or any other panel providing process (cairo-dock etc.)?

Comment 2 Thomas Lübking 2013-07-17 13:36:21 UTC

dev note: might be bug #322480

Comment 3 Milan Banjac 2013-09-13 08:15:21 UTC

Created attachment 82312 [details]
dual monitor setup

Comment 4 Milan Banjac 2013-09-13 08:15:39 UTC

I can confirm this bug is still present. Using Fedora 19/KDE 4.10.5 with monitor config shown in the attachment.
xrandr -q output:
Screen 0: minimum 320 x 200, current 3286 x 1297, maximum 8192 x 8192
LVDS1 connected primary 1366x768+0+529 (normal left inverted right x axis y axis) 344mm x 193mm
   1366x768       60.0*+
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        59.9  
VGA1 connected 1920x1080+1366+0 (normal left inverted right x axis y axis) 477mm x 268mm
   1920x1080      60.0*+
   1680x1050      60.0  
   1280x1024      75.0     60.0  
   1152x864       75.0  
   1024x768       75.1     60.0  
   800x600        75.0     60.3  
   640x480        75.0     60.0  
   720x400        70.1  
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)

Comment 5 Thomas Lübking 2013-09-13 12:05:26 UTC

Please check whether this is bug #322480 (for you)

The relevant output is that of

    xprop | grep -iC1 STRUT

on each panel on your screen, esp. panels on top and bottom and please elaborate on your results esp. regarding the OP comment:
> The mouse also is not restricted traveling out of bounds.

Because that rather indicates a "broken" screen setup (the logical screens exceed the physical ones) - mouse barriers are done by X11, not KWin.

Comment 6 Thomas Lübking 2013-10-12 12:28:11 UTC

@Giorgos, Milan
can you please check whether this is bug #322480 ?

Symptom:
- The window underruns the panel
- running "xprop | grep -iC1 STRUT" and clicking on the underran panel prints an insane number like "_NET_WM_STRUT(CARDINAL) = 0, 0, 4294966891, 0" instead of sth. nice like "_NET_WM_STRUT(CARDINAL) = 0, 0, 32, 0"

Comment 7 Andrew Crouthamel 2018-09-25 03:36:35 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 8 Andrew Crouthamel 2018-10-27 02:42:47 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!