Bug 17772 - An internal system error has occured
Summary: An internal system error has occured
Alias: None
Product: PackageKit
Classification: Unclassified
Component: backend-yum (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: lowest trivial
Assignee: Richard Hughes
QA Contact:
Depends on:
Reported: 2008-09-25 11:26 UTC by Eiver
Modified: 2008-10-13 06:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Eiver 2008-09-25 11:26:20 UTC
I use Fedora 9 with PackageKit and have all updates installed from standard Fedora repositories. Today Package Kit reported new updates to be installed. The installation fails during "Testing Changes" faze with the following error:

An internal system error has occurred
A problem that we were not expecting has occurred.
Please report this bug at http://bugs.freedesktop.org with the error description.

More details:

Error Type: <type 'exceptions.TypeError'>
Error Value: sequence item 0: expected string, tuple found
  File : /usr/share/PackageKit/helpers/yum/update-packages.py , line 19, in <module>
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1083, in update_packages
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1163, in _runYumTransaction
    message = self._format_msgs(ye.value)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1109, in _format_msgs
    text = "

No updates are being installed. Closing PackageKit and running the update process again always fails in the same way.
Comment 1 Eiver 2008-09-26 12:01:50 UTC
Hmmm. It seams that the bug is no longer reproducible, although I have absolutlely no idea what has changed. All updates were applied successfully today. The list of packages to be updated did not change I think. Reducing the priority of the bug.
Comment 2 Richard Hughes 2008-10-13 06:33:28 UTC
Please reopen if you can reproduce. Thanks.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.