#1252 Rosegarden doesn't remember size when maximized

Third Party Bugs
gui (282)

Bug Description
If I don't maximize Rosegarden, it remembers its window size when I close it and reopen it again. However, if I maximize Rosegarden, then the next time I open it, Rosegarden is no longer maximized, and it is resized to take up about 65% of the screen vertically. My resolution is 1280 x 960.

My System
Motherboard: MSI K9N SLI Platinum (nForce 570 SLI chipset)
CPU: AMD Athlon(tm) 64 Processor 4000+ (2.6 GHz)
Video: Dell NVIDIA GeForce 7800 GTX w/ 256 MB RAM (PCI Express)
OS: Kubuntu 9.10 i386 (with KDE SC 4.4)
Linux Kernel: 2.6.31-9-rt
NVIDIA driver: 185.18.36
Screen Resolution: 1280 x 960
X.org: 7.4
Qt version: 4.6.1


  • D. Michael McIntyre

    I can repeat this here with a completely different setup.

    This must be a Qt bug, because all we're doing is making a textbook Qt call to store and recall the window geometry. Maybe we can work around this through some hackery.

  • D. Michael McIntyre

    I investigated putting a potential workaround in 10.02.1, but I'm not comfortable doing something like that on the spur of the moment, without thorough testing.

    In the meantime, if you manually resize the window to be just a fraction smaller than full-screen, it will restore to the correct size. I find it needs to be 5-10 px smaller than the maximum possible to avoid tripping the (Qt) "restore maximized" code, which obviously calculates incorrectly.

    It's worth looking into Qt's source to see how this works, and whether there's a more tidy way around this trouble. (Or better yet, they fixed it in 4.6.)

  • S. Christian Collins

    FWIW, I am running with Qt 4.6.1, and I have the problem. Interestingly, this bug does not exhibit itself under LXDE, only KDE (I haven't tried other desktop environments).

  • D. Michael McIntyre

    Nope. They didn't fix it in 4.6, or 4.7. It restores full width horizontally only.

  • D. Michael McIntyre

    • status: open --> wont-fix
    • milestone: --> Third Party Bugs
  • D. Michael McIntyre

    This is Qt's and/or KDE's fault, and can be worked around. I say live with it.


Log in to post a comment.