After prompt for updates, if I select Show and Review, a "Getting Description" message is displayed, and then a crash box appears, containing: Error Type: <type 'exceptions.AttributeError'> Error Value: Updates instance has no attribute 'obsoletes' File : /usr/share/PackageKit/helpers/yum/get-update-detail.py , line 17, in <module> backend.get_update_detail(package) File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1490, in get_update_detail obsolete = self._get_obsoleted(pkg.name) File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1400, in _get_obsoleted obsoletes = self.yumbase.up.getObsoletesTuples(newest=1) File : /usr/lib/python2.5/site-packages/rpmUtils/updates.py , line 568, in getObsoletesTuples obslist = self.obsoletes.keys() Version is PackageKit-libs-0.2.5-1.fc9.i386 PackageKit-0.2.5-1.fc9.i386 I was unable to enter these values in the Version field of this form.
Can you please tell me which repos you have enabled please? Thanks.
Fedora 9 - i386 Fedora 9 - i386 Updates Fedora 9 - i386 Updates Newkey Livna for Fedora Core 9 -i386 - Base Shall I try turning on just one at a time?
Bug occurs with just Fedora 9 - i386 Updates Newkey enabled.
What package are you selecting to make it crash? Could you get me the output of: killall gpk-update-viewer gpk-update-viewer -v and then get it to crash? I just need to see the last 10 or so lines. Thanks.
Created attachment 18846 [details] [review] what's in git You can apply this patch doing: cd /usr/share/PackageKit/helpers/yum/helpers patch -p3 < pk-getObsoletesTuples-workaround.patch This should at least get rid of the backtrace, although I would like to see the real cause.
Created attachment 18848 [details] Messages in error window
Created attachment 18849 [details] Typescript from running the commands suggested (contains display escape codes in up-arrow form) I made a typescript, and am showing what I think are the lines of interest. I have removed the display code representations. I note, in the fourth line from the top of my excerpt, "client_error_code_cb,708", which did not appear in the error display window: TI:09:24:54 TH:0x8a1f3f0 FI:gpk-animated-icon.c FN:gpk_animated_icon_update,127 - polling check TI:09:24:54 TH:0x8a1f3f0 FI:pk-client.c FN:pk_client_error_code_cb,708 - emit error-code 3, Error Type: <type 'exceptions.AttributeError'> Error Value: Updates instance has no attribute 'obsoletes' File : /usr/share/PackageKit/helpers/yum/get-update-detail.py , line 17, in <module> backend.get_update_detail(package) File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1490, in get_update_detail obsolete = self._get_obsoleted(pkg.name) File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1400, in _get_obsoleted obsoletes = self.yumbase.up.getObsoletesTuples(newest=1) File : /usr/lib/python2.5/site-packages/rpmUtils/updates.py , line 568, in getObsoletesTuples obslist = self.obsoletes.keys() TI:09:24:54 TH:0x8a1f3f0 FI:pk-task-list.c FN:gpk_task_list_error_code_cb,193 - emit error-code TI:09:24:54 TH:0x8a1f3f0 FI:pk-client.c FN:pk_client_error_code_cb,708 Type: <type 'exceptions.AttributeError'> Error Value: Updates instance has no attribute 'obsoletes' File : /usr/share/PackageKit/helpers/yum/get-update-detail.py , line 17, in <module> backend.get_update_detail(package) File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1490, in get_update_detail obsolete = self._get_obsoleted(pkg.name) File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1400, in _get_obsoleted obsoletes = self.yumbase.up.getObsoletesTuples(newest=1) File : /usr/lib/python2.5/site-packages/rpmUtils/updates.py , line 568, in getObsoletesTuples obslist = self.obsoletes.keys() TI:09:24:54 TH:0x8a1f3f0 FI:gpk-animated-icon.c FN:gpk_animated_icon_update,127 - polling check
Created attachment 18850 [details] Typescript after applying patch Tried the patch. I had to use cd /usr/share/PackageKit/helpers/yum in order to apply it. I have included the resulting typescript, in case it is useful.
Cool, 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.