Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Extra Pane fails to reopen and shows error if previously opened folder no longer exists

Open
#3,742 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
desktop

Research direction

Reproduce the F3 → F3 sequence on Linux Mint 22.3 with Nemo 6.6.3, including deleting the folder previously opened in the Extra Pane. Trace the Extra Pane reopen and folder-restoration handling; done means the error is displayed if appropriate and the Extra Pane still opens on the folder shown in the main pane.

Written by the indexing model from the issue text.

Description

Distribution

Linux Mint 22.3 Zena

Package version

nemo 6.6.3

Frequency

Always

Bug description

Currently, when reopening the Extra Pane (F3 → F3 → F3), Nemo restores the folder that was previously open in the Extra Pane instead of matching the folder shown in the main pane, as described in .

If that previously opened folder no longer exists, Nemo shows an error message stating that the folder cannot be found, and the Extra Pane does not reopen.

Steps to reproduce
  • Press F3 to open the Extra Pane.
  • Click the Extra Pane to focus it.
  • Create a new folder in the Extra Pane.
  • Open that folder in the Extra Pane.
  • Click the main pane to switch focus.
  • Press F3 to close the Extra Pane.
  • Delete the folder that was created.
  • Press F3 again: an error message appears stating the folder no longer exists, and the Extra Pane does not reopen.
Expected behavior

In the final step, after displaying the error message, the Extra Pane should open the same folder currently shown in the main pane.

Additional information

No response

Dominant language
C
Stars
1.6k
Forks
373
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo

All issues in linuxmint/nemo

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.