id summary reporter owner description type status priority milestone component version resolution keywords cc blockedby blocking branch_state votes 4000 mc 4.8.23 - extfs data in /tmp/mc-USERNAME not deleted after closing mc (rpm/cpio + deb) ak andrew_b "Since updating to mc 4.8.23 some (but not all, see below) temporary data created in /tmp/mc-username is no longer being deleted after closing mc. This affects .rpm (cpio?) and .deb files, tar.gz/xz/bz2 do not seem to be affected though. Example (RPM file): - Navigate to a directory containing rpm files. - Select a rpm file and press , you will get sth. like this and /tmp/mc-username ist still empty: {{{ |/INFO │ 0│31. Mai 2018 ││ │ │ │ │ CONTENTS.cpio │ 0│31. Mai 2018 ││ │ │ │ │ HEADER │ 859│31. Mai 2018 ││ │ │ │ │*INSTALL │ 0│31. Mai 2018 ││ │ │ │ │*REBUILD }}} If you now select ""CONTENTS.cpio"" and hit again, you will see the files inside the rpm (which as you might know are packed as a cpo archive), and inside /tmp/mc-username a respcetive file extfsCONTENTS.cpio is created. After closing mc, the file /tmp/mc-username/extfsCONTENTS.cpio is no longer deleted like in older versions of mc (up to 4.8.22). I also tested some deb-packages with similar results: Navigate to some deb-package -> press -> select ""CONTENTS"" folder -> navigate to some file, press F3 to show contents -> /tmp/mc-username/extfs-somename is created and not deleted after closing mc. As indicated before, version 4.8.22 deletes these temporary files after closing mc, which in my opinion should be the ""correct"" way of dealing with such temporary files. Greetings, AK " defect closed major 4.8.24 mc-vfs 4.8.23 fixed extfs info@… merged committed-master