Width and Height Double Entries in Configuration Files. In particular configuration files in "~/.kde/share/config" 'width' and 'height' entries are doubled up in some definition segments which on my system is causing windows to no save their dimensions. I've tried deleting the '~/.kde' but problem persists. I had the problem with Kubuntu 13.04 and upgrade to 13.10 and the problem exists. Reproducible: Always Steps to Reproduce: 1. Window dimensions don't save 2. Check configuration files and notice segments with 2x height and 2x widths field entries. 3. Try to fix but innate problem Actual Results: Windows refuse to save one dimension set of data. Expected Results: Only store one set of height and width data else the last or first is only used and may not be updated
Unrelated to the Windowmanager. This is done by KMainWindow and it stores Width and Height per screen dimension, eg. Width 1024=449 Width 1920=821 Height 768=321 Width 1200=512 That is not a bug. -> Please provide an rc you cosider buggy as well as the output of "xrandr -q" Ensure you've not setup a rule for KWin in "kcmshell4 kwinrules" to remember window sizes (and NO: setting up ONE rule for ALL windows to have the WM manage window sizes does NOT work. The rules have to match exactly, otherwise the last closed window impacts all other matching ones. Size remembering is in general a client job, rules exist to "fix" particular clients)
(In reply to comment #1) > Unrelated to the Windowmanager. > > This is done by KMainWindow and it stores Width and Height per screen > dimension, eg. > Width 1024=449 > Width 1920=821 > Height 768=321 > Width 1200=512 > > That is not a bug. > > -> Please provide an rc you cosider buggy as well as the output of "xrandr > -q" > > Ensure you've not setup a rule for KWin in "kcmshell4 kwinrules" to remember > window sizes (and NO: setting up ONE rule for ALL windows to have the WM > manage window sizes does NOT work. The rules have to match exactly, > otherwise the last closed window impacts all other matching ones. Size > remembering is in general a client job, rules exist to "fix" particular > clients) I posted a similar question on KDE forums and the thread was moved into the KWin area, so that is why I posted the bug under this category. Second, I get your point about different resolutions. I have a problem with windows not saving their dimensions, and thought this maybe the reason. There are no rules in my setup. I want the default mannerism of KDE, which is to naturally save its window height and widths. Next time, consider if your reply comes across as rude and abrupt, as to me it did. This type of sentiment will scare people off reporting.
Please do not quote but for inline reply, you're mailing to a bugtracker. (In reply to comment #2) > I posted a similar question on KDE forums and the thread was moved into the > KWin area, so that is why I posted the bug under this category. Yes i saw that, but it doesn't change anything about how things are. > Second, I get your point about different resolutions. I have a problem with > windows not saving their dimensions, and thought this maybe the reason. It might be involved if you've a multiscreen setup. (what the "xrandr -q" output would have shown) > I want the default mannerism of KDE, which is to naturally save its window > height and widths. Please notice again that this is not a KDE "mannerism" by itself. Each client (eg. also Firefox or Libreoffice) has to maintain that by itself, therefore a specification of actual clients failing on this is mandatory. > Next time, consider if your reply comes across as rude and abrupt, as to me > it did. Mind elaborating on what you'd consider "rude" or "abrupt"? No idea what you expect, but I just stated a fact about the bug assignment, explained why you see multiple Width/Height entries in the RCs, asked for some additional info and wanted to ensure that you're not running into a misassumption about the KWin rule system.
> (what the "xrandr -q" > output would have shown) xrandr -q=== Screen 0: minimum 8 x 8, current 1920 x 2250, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 60.0*+ 1440x900 75.0 59.9 1280x1024 75.0 60.0 1024x768 75.0 70.1 60.0 800x600 75.0 72.2 60.3 640x480 75.0 72.8 59.9 HDMI-0 connected primary 1920x1200+0+1050 (normal left inverted right x axis y axis) 546mm x 352mm 1920x1200 60.0*+ 1920x1080 60.0 60.0 59.9 50.0 60.1 60.0 50.0 1680x1050 60.0 1600x1200 60.0 1440x900 59.9 1366x768 59.8 1280x1024 75.0 60.0 1280x960 60.0 1280x720 60.0 59.9 50.0 1152x864 75.0 1024x768 75.0 70.1 60.0 800x600 75.0 72.2 60.3 56.2 720x576 50.0 720x480 59.9 640x480 75.0 72.8 59.9 59.9 DP-0 disconnected (normal left inverted right x axis y axis) DVI-D-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) > Mind elaborating on what you'd consider "rude" or "abrupt"? Reply text of 1 to 2k isn't the end of the world. I fathom it could become a pain if everyone did it all the time. I'm not new to forum quotation, it was something that happened ,but the way you come across was demeaning as if everything I offered was unworthy. One could say, why bother. Maybe I'm touchy, as other bugs I've reported have been undermined. I don't program in QT/QML, so I'm not aware of the API's or application core's to KDE. I just tell this bug tracker what I'm experiencing. It then is up to someone else to investigate.
(In reply to comment #4) > Screen 0: minimum 8 x 8, current 1920 x 2250, maximum 16384 x 16384 > DVI-I-0 disconnected (normal left inverted right x axis y axis) > DVI-I-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) > HDMI-0 connected primary 1920x1200+0+1050 (normal left inverted right x axis > y axis) 546mm x 352mm You'll likely just experience bug #286146, that is, you close the window on the lower screen (1920x1200) but it initially opens on the upper screen (1680x1050) and reads/restores the size for that screen (maybe the other way round) The window might be moved to the other screen afterwards. The important thing to check is that the size for the other screensize is restored. -> Confirmable? > Reply text of 1 to 2k isn't the end of the world. I fathom it could become > a pain if everyone did it all the time. Check the webpage linked on top of the mail. It's not about wasting precious server space, but bugs can become very hard to read in that representation if there's massive quoting. > was something that happened ,but the way you come across was > demeaning as if everything I offered was unworthy. Be assured that whenever i consider somebody or something "unworthy", i'll just say so.
If you can reproduce it with a KDE application, please add the contents of the .kde/share/config/applicationrc file.
If you can provide the information requested in comment #6, please add it.
To further investigate this issue, KDE developers need the information requested in comment #6. If you can provide it, or need help with finding that information, please add a comment.
(In reply to comment #8) > To further investigate this issue, KDE developers need the information > requested in comment #6. If you can provide it, or need help with finding > that information, please add a comment. The problem seems that if you have screens of different physical dimensions (set resolution) KDE save the dimensions correctly when closing a window per screen, but when the user opens that window up it is sized to the first screen set in the ~/.kde/share/config file of that application rather than the screen it's opening on. Other words KDE is not respecting which monitor the window is opened on and using that set of dimensions previously saved. Example of my live konsolerc segment; #============================ [MainWindow] Width 1680=700 Height 1050=500 Width 1920=200 Height 1200=100 State=AAAA/wAAAAD9AAAAAAAAANUAAACVAAAABAAAAAQAAAAIAAAACPwAAAAA ToolBarsMovable=Disabled #============================ Now if I open the konsole in my monitor that is 1920X1200, the konsole window will be 700x500 not the proper 200x100 I last left it.
The title and first bug entry is erroneous to the real problem. The double entries are normal and proper.
*** This bug has been marked as a duplicate of bug 286146 ***