Bug 185513 - Maximizing windows not working correctly on xrandr multiscreen setup
Summary: Maximizing windows not working correctly on xrandr multiscreen setup
Status: RESOLVED FIXED
Alias: None
Product: kephal
Classification: Unmaintained
Component: General (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Aike J Sommer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-25 11:33 UTC by Daniel Mader
Modified: 2009-04-20 11:57 UTC (History)
0 users

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


Attachments
screenshot showing the weird window placement (136.42 KB, image/png)
2009-02-25 11:36 UTC, Daniel Mader
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Mader 2009-02-25 11:33:26 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

There are still bugs in the handling of multiscreen setups.

After creating a multiscreen setup with xrandr, the panel is located on the left screen, which I like. Yet, windows think the panel is on the right screen.

This leads to annoying behavio when windows are positioned or when they are maximized, since on the left screen they disappear behind the panel, while on the right screen they always omit the space where they think the panel is.

A workaround is to drag the panel to another screenedge and back to the desired location, then windows are aware of the proper position.
Comment 1 Daniel Mader 2009-02-25 11:36:08 UTC
Created attachment 31631 [details]
screenshot showing the weird window placement

This shot has been created right after the dual screen setup has been created. The opened windows do think the panel is on the right screen, while in fact it is on the left screen.
Comment 2 Daniel Mader 2009-02-28 17:28:06 UTC
There seems to be a fix available in trunk:
http://identi.ca/notice/2450245
Comment 3 Daniel Mader 2009-04-20 11:57:31 UTC
It is fixed in openSUSE 11.1 (KDE4 factory) and Mandriva 2009.1 RC2, so I guess this bug can be closed.