Red Hat Bugzilla – Bug 492837
Internal system error on package installation
Last modified: 2014-09-22 11:56:05 EDT
Description of problem:
Trying to install a couple of packages with gnome-packagekit, I'm getting an internal system error.
Version-Release number of selected component (if applicable):
sometimes, say one out of ten times
Steps to Reproduce:
1. Fresh install with all updates applied
2. Try to install something with gnome-packagekit
gpk-application hangs, nothing happens: No cpu load, no network traffic. After a while an error message appears:
An internal system error occurred
A problem that we were not expecting has occurred.
Please report this bug in your distribution bug tracker with the error description.
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2311, in main
File : /usr/lib/python2.5/site-packages/packagekit/backend.py, line 600, in dispatcher
File : /usr/lib/python2.5/site-packages/packagekit/backend.py, line 517, in dispatch_command
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1217, in install_packages
pkg, inst = self._findPackage(package)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 745, in _findPackage
pkgs = self.yumbase.pkgSack.searchNevra(name=n, epoch=e, ver=v, rel=r, arch=a)
File : /usr/lib/python2.5/site-packages/yum/__init__.py, line 592, in <lambda>
pkgSack = property(fget=lambda self: self._getSacks(),
File : /usr/lib/python2.5/site-packages/yum/__init__.py, line 435, in _getSacks
File : /usr/lib/python2.5/site-packages/yum/repos.py, line 251, in populateSack
sack.populate(repo, mdtype, callback, cacheonly)
File : /usr/lib/python2.5/site-packages/yum/yumRepo.py, line 174, in populate
File : /usr/lib/python2.5/site-packages/yum/misc.py, line 589, in bunzipFile
s_fn = bz2.BZ2File(source, 'r')
I've never seen this error before. If you do "yum clean all" and then retry, does this fix things?
I did not try, I used "Refresh package lists" from the menu and the error disappeared.
From your last update, it looks like things are back to normal. We consider that a reasonable amount of time has passed between the first time the bug occurred and now. Since the bug is not reproducible again, I am closing this bug out now.
In case you face the similar issue again, please open a bug report with the exact steps you did to reproduce it. It would be more helpful, if you can also try the command from comment #1 and also update us if that worked on the new bug if you open one.
Fedora Bugzappers volunteer triage team
(In reply to comment #3)
> Hi Christoph,
> From your last update, it looks like things are back to normal. We consider
> that a reasonable amount of time has passed between the first time the bug
> occurred and now.
You call 5 days a reasonable amount of time? Given the fact that you only refresh you package list once a day the package lists have been refreshed only four times.
> Since the bug is not reproducible again, I am closing this bug out now.
Gireesh, I doubt that this kind of bugzapping is really helpful. Bugzilla is for tracking bugs and not for housekeeping.
> In case you face the similar issue again, please open a bug report with the
> exact steps you did to reproduce it.
I think I already gave a detailed description, what exactly is missing in your opinion? Why did you flag the bug NEEDINFO if you closed it anyway? And why should I open a new bug? It can better be tracked here because this bug marks it's first appearance.
The error message tells the user to report the bug to the developers and that's what I did. Richard said that he has never seen this bug before, so this should be investigated or even better get fixed (e.g. by automatically making gpk refresh the package lists if there is something wrong with them).
> It would be more helpful, if you can also
> try the command from comment #1 and also update us if that worked on the new
> bug if you open one.
Of course 'yum clean all' will fix the bug because afterwards you have to refresh software sources again - and this is what packagekit did when I selected 'Refresh package lists' from the menu. Are you really sure you know what's going on here?