Bug 550199
Summary: | Software Installer reports an internal system error | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Fraser <david_fraser> |
Component: | PackageKit | Assignee: | Richard Hughes <richard> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | balajig81, gs06897, kevin, ltinkl, rdieter, richard, smparrish |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-12-27 17:38:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Fraser
2009-12-23 23:59:34 UTC
not sure how best to triage this, but as the traceback only mentions PackageKit... Were you using kpackagekit (KDE) or gnome-packagekit (Gnome)? I've seen this happen with kpackagekit when applying the current F12 updates, including xine-lib-1.1.16.3-5.fc12. The obsoletion of xine-lib-pulseaudio might be confusing PackageKit. Actually, I saw 3 strange things happen: 1. The confirmation dialog listed the packages as to be removed when they were actually to be upgraded. 2. I got a dialog complaining about an unknown error. 3. I got the above backtrace. ok, let's go with kpackagekit for now. I was using gpk-update-viewer (Gnome). alrighty, PackageKit is common to both (the exception seemed to be in the pk yum backend code). Same issue here when using gpk-update-viewer to install updates. Seems to resolve dependencies and then throws the error: Error Type: <class 'yum.Errors.RepoError'> Error Value: Error getting repository data for installed, repository not found File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in <module> main() File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main backend.dispatcher(sys.argv[1:]) File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 710, in dispatcher self.dispatch_command(args[0], args[1:]) File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 657, in dispatch_command self.update_packages(only_trusted, package_ids) File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1948, in update_packages signed = self._is_package_repo_signed(pkg) File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1437, in _is_package_repo_signed repo = self.yumbase.repos.getRepo(pkg.repoid) File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo 'Error getting repository data for $s, repository not found' $ (repoid) These are the yum/updater-related packages I have on the system: kpackagekit-0.5.1.1-1.fc12.x86_64 gnome-packagekit-2.28.2-0.2.20091116git.fc12.x86_64 yum-presto-0.6.1-1.fc12.noarch anaconda-yum-plugins-1.0-5.fc12.noarch yum-3.2.25-1.fc12.noarch yum-metadata-parser-1.1.2-14.fc12.x86_64 PackageKit-yum-0.5.4-0.4.20091029git.fc12.x86_64 yum-utils-1.1.24-2.fc12.noarch PackageKit-yum-plugin-0.5.4-0.4.20091029git.fc12.x86_64 *** This bug has been marked as a duplicate of bug 541645 *** |