Description of problem: dnfdragora 2.1.0 is starting in full-screen (maximized) mode. This started to occur either with the F32 to F33 upgrade or with updates very shortly after. Everything works fine, but it is bothersome to have to resize the window each time. Version-Release number of selected component (if applicable): dnfdragora 2.1.0 Mate 1.24.1 Fedora 33 How reproducible: Consistently Steps to Reproduce: 1. Start dnfdragora from command line or menu 2. Observe app opening in maximized state 3. All subsequent functions work and unmaximized state can be obtained using the "Restore Window" "button". Actual results: dnfdragora starts in full-screen (maximized) mode. Expected results: dnfsragora starts in un-maximized mode Additional info: ----- Console transcript ----- $ dnfdragora Try reading configuration file From ./dnfdragora.yaml Skipped exception: <[Errno 2] No such file or directory: './dnfdragora.yaml'> From /etc/dnfdragora/dnfdragora.yaml Finally read user settings from /home/rengland/.config/dnfdragora.yaml <_M_> [ui] YUILoader.cc:60 loadUI(): DISPLAY: ":0" <_M_> [ui] YUILoader.cc:61 loadUI(): XDG_CURRENT_DESKTOP: "MATE" <_M_> [ui] YUILoader.cc:62 loadUI(): YUI_PREFERED_BACKEND: "" <_M_> [ui] YUILoader.cc:74 loadUI(): Detected a Gtk-based desktop environment. <_M_> [ui] YUILoader.cc:74 loadUI(): Prefering Gtk-UI if available and no <_M_> [ui] YUILoader.cc:74 loadUI(): user-selected override is present. <_M_> [ui] YUILoader.cc:96 loadUI(): User-selected UI-plugin: "" <_M_> [ui] YUILoader.cc:128 loadUI(): Using UI-plugin: "gtk" <_M_> [ui] YUI.cc:81 YUI(): This is libyui 3.10.0 <_M_> [ui] YUI.cc:82 YUI(): Creating UI without threads <_M_> [gtk] YGUI.cc:48 YGUI(): This is libyui-gtk 2.49.0 <_M_> [gtk] YGUI.cc:166 checkInit(): Style "/usr/share/libyui/theme/current/wizard/style.css" <_M_> [gtk] YGUI.cc:188 checkInit(): Style "/usr/share/libyui/theme/current/wizard/style.css" not found. Ignoring style <WRN> [gtk] YGUtils.cc:543 loadPixbuf(): Could not load icon: /usr/share/libyui/theme/icons/32x32/apps/yast.png <WRN> [gtk] YGUtils.cc:543 loadPixbuf(): Reason: Failed to open file “/usr/share/libyui/theme/icons/32x32/apps/yast.png”: No such file or directory <_M_> [ui] YUI.cc:236 topmostConstructorHasFinished(): Running without threads <_M_> [ew] YExternalWidgets.cc:40 YExternalWidgets(): Creating Libyui External Widgets object <ERR> [Gtk] libyui-gtk:0 (): gtk_window_set_default_size: assertion 'width >= -1' failed <ERR> [Gtk] libyui-gtk:0 (): gtk_window_resize: assertion 'width > 0' failed <_M_> [gtk] YMGA_GCBTable.cc:414 YMGA_GCBTable(): Slection mode 2 <_M_> [gtk] YMGA_GCBTable.cc:433 YMGA_GCBTable(): columns 8 tot 8 Get root backend. Locked (False) Get root backend. Locked (False) End found 1 groups <_M_> [ui] YUILoader.cc:234 deleteUI(): Shutting down UI <_M_> [ew] YExternalWidgets.cc:123 ~YExternalWidgetsTerminator(): Shutting down mga External Widgets <_M_> [ew] YMGAWidgetExtensionFactory.cc:49 ~YMGAWidgetFactory(): Factory removed
I have subsequently found that if I use the CLI with the option --qt I see the non-maximized view that was appearing earlier. $ dnfdragora --qt
Maybe a quick interim fix would be to add "--qt" to the desktop launcher (which I've just done locally) pending a real fix later.
FYI Fedora 34 beta branch has this issue also.
The Fedora 34 release has this issue also. I am using MATE Desktop. Does it only happen with MATE Desktop?
No it isn't MATE specific, it's doing it on other desktop environments also (Xfce in my case).
This should be assigned to Fedora 34 or the bug will die then 33 goes EOL.
This issue is in the Fedora 36 beta branch also.
If I'm not mistaken this is now fixed in the Fedora 36 Beta Branch. I didn't see this issue testing Xfce/LXQt/MATE using the Beta 1.1 or Beta 1.2 test composes images.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
Fixed in FL36-37