Bug 284207

Summary: saved window sizes overridden by one monitor's settings
Product: [I don't know] kde Reporter: wes <cdbroad>
Component: dualheadAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED FIXED    
Severity: major CC: iivanich, kde, nate
Priority: NOR    
Version: 4.11.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In: 5.74

Description wes 2011-10-16 17:45:45 UTC
Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

In kde rc files and profiles files (e.g. konqueror's webbrowsing profile) window sizes are stored like this:

Height 1024=850
Height 1050=920
Width 1280=1000
Width 1680=979

But when I restart an application, the restored window is *always* the size stored for my left monitor (i.e. 1024x1050).



Reproducible: Always

Steps to Reproduce:
just adjust window size on right monitor, close app, reopen and it restores to size stored for *left* monitor

Actual Results:  
as above, apps open in right monitor with window size that was stored for the right monitor

Expected Results:  
I expect/want the window size to be remembered for each monitor and restored to each monitor appropriately (this is the way KDE worked before 4.7 as far as I can tell)
Comment 1 wes 2011-10-16 17:48:26 UTC
under "actual results" sorry for the typo - the second "right" should of course be "left"
Comment 2 ml 2011-11-26 21:03:52 UTC
According to bug 286146.
> on a last note: "kate, dolphin, konsole,ktorrent,kmail, akregator" as well as
> konqueror (on bug 284207 and at least if called through kfmclient) all only run
> in one process by default - this could really matter.
> If you cannot reproduce it with eg. kwrite (which does also NOT spawn new
> instances if you use the "open" menu but should if you call it as usual, like
> through krunner or from konsole etc.) we'd have an important hook.

I've tested it with kwrite and behavior the same as with other kde applications.
Comment 3 Nate Graham 2020-09-09 03:04:03 UTC
Oh hey, I just fixed this recently! The fix is in Frameworks 5.74.