Hide Forgot
Created attachment 590718 [details] Smolt profile + other abrt collected information attached. Description of problem: I tried hitting 'tab' to autocomplete my yum install command, and this error popped up. Version-Release number of selected component (if applicable): How reproducible: Everytime. Steps to Reproduce: 1. Open a terminal and type out 'sudo yum install k' 2. Hit tab to complete. 3. Actual results: This error pops up. Expected results: That the field should autocomplete or show suggestions. Additional info: The file that it cannot access "yumRepo.py:614:_dirSetupMkdir_p:RepoError: Cannot access repository dir /var/tmp/yum-krishna-HeA4lf/i386/17/fedora" does not exist in my computer. The folder yum-krishna-HeA4lf is completely empty. I am running a virtualized LXDE F17 i686.
Thanks for the report, I'll fix it soon. As a workaround, just run "yum makecache" as a user. That should make Tab-completion work.
*** Bug 831043 has been marked as a duplicate of this bug. ***
*** Bug 832841 has been marked as a duplicate of this bug. ***
*** Bug 832756 has been marked as a duplicate of this bug. ***
yum-3.4.3-28.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/yum-3.4.3-28.fc17
*** Bug 835583 has been marked as a duplicate of this bug. ***
*** Bug 835754 has been marked as a duplicate of this bug. ***
*** Bug 835690 has been marked as a duplicate of this bug. ***
*** Bug 835638 has been marked as a duplicate of this bug. ***
*** Bug 835615 has been marked as a duplicate of this bug. ***
*** Bug 835871 has been marked as a duplicate of this bug. ***
*** Bug 835888 has been marked as a duplicate of this bug. ***
yum-3.4.3-28.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 858860 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
yum-3.4.3-102.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/yum-3.4.3-102.fc19
Package yum-3.4.3-102.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing yum-3.4.3-102.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-13246/yum-3.4.3-102.fc19 then log in and leave karma (feedback).
yum-3.4.3-102.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.