Skip to content

Menu becomes invisible after screen resize #5184

Closed

Description

@mc-worker

Is there an existing issue for this?

  • I have searched the existing issues

Midnight Commander version and build configuration

Current master 4.8.33-792-g32e3114bf

Operating system

Linux

Is this issue reproducible using the latest version of Midnight Commander?

  • I confirm the issue is still reproducible with the latest version of Midnight Commander

How to reproduce

  1. Make menubar invisible: switch Options -> Layout... -> Menubar visible off
  2. Press F9 to show menu bar.
  3. Change size of terminal emulator window.

Expected behavior

Menu should stay visible.

Actual behavior

Menu bar becomes invisible.

Additional context

This bug was introduced in 0e75e85.

Solution: change the visibility of main file manager widgets (menu bar, hint bar, command line, and key bar) only if these states are really changed by use via "Layout" configuration dialog.

Activity

  1. added this to the 4.9.0 milestone on Oct 11, 2026
  2. self-assigned this
    on Oct 11, 2026
  3. added theissue type on Oct 11, 2026
  4. added
    area: coreIssues not related to a specific subsystem
    prio: mediumHas the potential to affect progress
    on Oct 11, 2026
  5. github-actions commented on Oct 11, 2026

    @github-actions

    The changes in the branch associated with this issue are ready for review.

  6. zyv commented on Oct 16, 2026

    @zyv
    Member

    These changes fix the original bug, but introduce two new ones:

    • Cancelling the Layout dialog leaves the keybar, command prompt, or hintbar in the cancelled state
    • When the keybar is hidden, the menubar disappears permanently after F9 -> Esc

    I have added 2 patches for both. In the second patch, the widget remembers its visibility state before activation instead of using mc_global.menubar_visible, because WMenuBar is also used by mcedit, whose menubar is always shown and ignores the filemanager option. Reading a global there would trade one wrong flag for another.

    Feel free to squash accordingly. Let me know if it helps (and if it doesn't). With the two bugs fixed in one way or another, I think this is good to merge.

  7. added
    state: approvedIf not using PRs: associated branch has been approved
    on Oct 16, 2026
  8. github-actions commented on Oct 16, 2026

    @github-actions

    The changes in the branch associated with this issue have been approved.

  9. added a commit that references this issue on Oct 17, 2026
  10. mc-worker commented on Oct 17, 2026

    @mc-worker
    ContributorAuthor

    These changes fix the original bug, but introduce two new ones:

    Indeed. :(

    I have added 2 patches for both [...]

    Feel free to squash accordingly.

    I did that.

    Let me know if it helps (and if it doesn't). With the two bugs fixed in one way or another, I think this is good to merge.

    Yes it helps. I'm ready to merge this branch.

  11. zyv commented on Oct 17, 2026

    @zyv
    Member

    Yes it helps. I'm ready to merge this branch.

    Well, then go ahead :) Thank you!

  12. added 2 commits that reference this issue on Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: coreIssues not related to a specific subsystemprio: mediumHas the potential to affect progress

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions