Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1443730 - mc can't not exit to its current directory
Summary: mc can't not exit to its current directory
Alias: None
Product: Fedora
Classification: Fedora
Component: mc
Version: 25
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 1433602
TreeView+ depends on / blocked
Reported: 2017-04-19 20:39 UTC by Daniel
Modified: 2017-12-12 10:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-12 10:15:32 UTC
Type: Bug

Attachments (Terms of Use)

Description Daniel 2017-04-19 20:39:52 UTC
Description of problem: Midnight Commander does not exit to its current directory anymore after exiting with F10. It jumps back to the directory where it was started.

Version-Release number of selected component (if applicable): 

How reproducible:

Steps to Reproduce:
1. start Midnight Commander from command line by hitting 'mc' 
2. maneuver to any other directory of the file system
3. hit 'F10' to exit Midnight Commander 
4. prove with 'pwd' that you haven't moved anywhere

Actual results: you haven't moved anywhere

Expected results: you should have moved to the directory where you went with mc

Comment 1 Daniel 2017-04-20 10:46:41 UTC
Interestingly this is already broken in version mc-4.8.18-4. Just recompiled mc-4.8.18-4.fc25.src.rpm on a F25 system with all updates and the Midnight Commander can't exit to its current directory. 
Recompiled mc-4.8.18-2.fc25.src.rpm (is actually the same without mc-tmpdir.patch) and it works again as it should.

Comment 2 Andrea 2017-04-22 19:16:06 UTC
I would say this is a dupl

Comment 3 Daniel 2017-04-26 06:41:28 UTC
Current version mc-4.8.19-1 works fine without mc-tmpdir.patch. Think, Andrea, you're right.

Comment 4 Armands Liepins 2017-05-09 13:29:33 UTC
This is because /usr/libexec/mc/ (and .csh) contains


and there is no directory /tmp/mc-$MC_USER anymore.
What could be the right fix for this?

Comment 5 vvs 2017-05-13 08:52:06 UTC
This is a duplicate of 1438149, 1433602 and it's not Fedora version or architecture specific. Those bugs were closed improperly without any actual fix.

Comment 6 Fedora End Of Life 2017-11-16 19:47:55 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Comment 7 Andrea 2017-12-02 20:28:48 UTC
I think this has long been fixed.

Comment 8 Fedora End Of Life 2017-12-12 10:15:32 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.