Description of problem: while trying to reproduce bug 1047479 I did the following steps: * cleared all yum (and dnf) cashes * removed hamster-time-tracker (yum remove ...), although this one is not required to reproduce * opened gnome-software - it was showing loading dots on the buttons * while the dots where showing, I entered "sudo yum install hams" into a terminal and hit the tab-key several times * abrt pops up either now, or when gnome-software seems not to respond, after gnome-software is closed Version-Release number of selected component: yum-3.4.3-128.fc20 Additional info: reporter: libreport-2.1.10 cmdline: /usr/bin/python -t /usr/share/yum-cli/completion-helper.py -d 0 -C list available hams dso_list: yum-metadata-parser-1.1.4-9.fc20.x86_64 executable: /usr/share/yum-cli/completion-helper.py kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: sqlitecachec.py:46:getPrimary:TypeError: Can not create db_info table: database is locked Traceback (most recent call last): File "/usr/share/yum-cli/completion-helper.py", line 95, in <module> main(sys.argv[1:]) File "/usr/share/yum-cli/completion-helper.py", line 88, in main base.doCommands() File "/usr/share/yum-cli/cli.py", line 570, in doCommands return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds) File "/usr/share/yum-cli/completion-helper.py", line 52, in doCommand patterns=[get_pattern(extcmds)]) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2933, in doPackageLists avail = self.pkgSack.returnNewestByNameArch(patterns=patterns, File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1071, in <lambda> pkgSack = property(fget=lambda self: self._getSacks(), File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 776, in _getSacks self.repos.populateSack(which=repos) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 383, in populateSack sack.populate(repo, mdtype, callback, cacheonly) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 260, in populate dobj = repo_cache_function(xml, csum) File "/usr/lib64/python2.7/site-packages/sqlitecachec.py", line 46, in getPrimary self.repoid)) TypeError: Can not create db_info table: database is locked Local variables in innermost frame: checksum: 'dc7e96010cef32e75fe341d4cd92c0ad0419586a' self: <sqlitecachec.RepodataParserSqlite instance at 0x1e33e60> location: '/var/cache/yum/x86_64/20/google-chrome/gen/primary.xml' Potential duplicate: bug 903814
Created attachment 847200 [details] File: backtrace
Created attachment 847201 [details] File: environ
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.