Bug 310933 - Bottom "screen edge" not activated with TwinView / multiple monitors with different resolutions
Summary: Bottom "screen edge" not activated with TwinView / multiple monitors with dif...
Status: RESOLVED DUPLICATE of bug 290887
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 4.9.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-30 15:22 UTC by Stefan Burnicki
Modified: 2012-12-07 00:22 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Burnicki 2012-11-30 15:22:00 UTC
I have a setup with two screens. The main screen on the left with a resolution of 1680x1050 and the one on the right with 1920x1080. By default these screens are aligned at the top of the big virtual screen.
However if I define a behavior when I touch the bottom screen edge (Workspace Behavior -> Screen Edges), this behavior is only activated on the bottom edge of the right screen.
If I define the opsition of both screens absolutely such that they are both aligned at the bottom of the big virtual screen, the behavior can be activated on both screens.

I'm using the proprietary nvidia driver 310.14 in "TwinView" mode for this, but I'm configuring the screen setup with the systemsettings module.

Seems to me as if the "bottom edge" of the screen is defined as the last n pixels of the big virtual one, which is wrong in this case, as it should be defined for each physical screen separately.

Reproducible: Always

Steps to Reproduce:
1. Choose a screen setup with different size in "extended mode", e.g. 1680x1050 and 1920x1080
2. Define the "workspace behavior" such that anything is activated if you try to touch the bottom screen.

Actual Results:  
The behavior is only activated on the larger physical screen, not on the smaller one.

Expected Results:  
The behavior should be activated on any of both screens, regardless whcih one and with which setup
Comment 1 Thomas Lübking 2012-12-07 00:22:40 UTC

*** This bug has been marked as a duplicate of bug 290887 ***