Created attachment 1176678 [details] Screen shot of tiny Emacs windows After upgrading to F24, doing "Emacs' to a remote X server has serious issues with the window sizes. Basically, it starts up fine at first, but then shrinks the window to a tiny little thing. I've tried various things, such as emacs -q # No init file emacs --geometry 150x100+125+0 # specific windows geometry In the second case, the window starts out in the right location and size, but then resizes itself (see attached SS). Again, I only see this when Emacs is connecting to a remote X server (my Mac's xquartz). I did go back to a F23 installation to try the same thing, and it does not reproduce there, so something definitely changed between F23 -> F24. I'm not seeing the same issue with the other apps, e.g. Firefox. I hope this report makes any sense, please let me know if you need more details.
This used to happen before F24 was released (https://bugzilla.redhat.com/show_bug.cgi?id=1332451). It doesn't happen for me anymore, but I'm not using remote X. I also noticed that the upstream fixed it a bit differently than what the original patch was. I'll provide a testing package with the original patch applied.
Please, try with the packages from https://jsynacek.fedorapeople.org/emacs/bz1353063/.
I tried those RPMs, but it still behaves the same :/. I'm attaching a 2s video that shows the exact behavior (it starts first with the right / specified size, and then resizes). It behaves the same if I start with "emacs -q" (no init files).
Created attachment 1179892 [details] Video screenshot (2s)
Yes, that's exactly what was happening earlier. @Matthias: Any idea, why the emacs patch wouldn't work with remote X11?
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still the same issue in F26.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.