Description of problem: There is error dialog everytime the archive is opened (various archives, not only tar.gz). The archive is opened OK, but the error dialog is annoying. I am getting the error dialog even with clear profile (new user added). There was no such dialog in previous versions of MC, thus it seems to be an regression in MC. Version-Release number of selected component (if applicable): mc-4.8.3-1.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1. Open archive.tar.gz in MC Actual results: Error: Cannot open tar archive archive.tar.gz/ugz:// (but in the final the archive is opened OK) Expected results: No error message Additional info:
It seems fixed in mc-4.8.4-2.fc17.x86_64 (https://admin.fedoraproject.org/updates/FEDORA-2012-10976/mc-4.8.4-2.fc17)
mc-4.8.4-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-10976/mc-4.8.4-2.fc17
mc-4.8.5-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mc-4.8.5-1.fc18
mc-4.8.5-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mc-4.8.5-1.fc17
mc-4.8.5-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mc-4.8.5-1.fc16
Package mc-4.8.5-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mc-4.8.5-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-13795/mc-4.8.5-1.fc18 then log in and leave karma (feedback).
mc-4.8.5-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
mc-4.8.5-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
mc-4.8.5-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.