Bug 318264 - Apper Error When Searching Updates
Summary: Apper Error When Searching Updates
Status: RESOLVED WORKSFORME
Alias: None
Product: apper
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR grave
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-12 20:44 UTC by KitchM
Modified: 2022-12-08 05:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
File '/repodata/repomd.xml' not found on medium - info after starting apper (75 bytes, text/plain)
2017-08-29 16:09 UTC, karlo pasemann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description KitchM 2013-04-12 20:44:10 UTC
Selecting apper and then double-clicking the updates icon returns the following error message:
Traceback (most recent call last): File "/usr/share/PackageKit/helpers/yum/yumBackend.py", line 2714, in get_updates ygl = self.yumbase.doPackageLists(pkgnarrow='obsoletes') File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2787, in doPackageLists instpo = self.getInstalledPackageObject(instTup) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3881, in getInstalledPackageObject raise Errors.RpmDBError, _('Package tuple $s could not be found in rpmdb') $ str(pkgtup) RpmDBError: Package tuple ('eject', 'x86_64', '0', '2.1.5', '22.fc17') could not be found in rpmdb 

Reproducible: Always

Steps to Reproduce:
1.  Follow steps outlined above.
2.
3.
Actual Results:  
Error message

Expected Results:  
No error messages
Comment 1 karlo pasemann 2017-08-29 16:09:52 UTC
Created attachment 107580 [details]
File '/repodata/repomd.xml' not found on medium - info after starting apper

File '/repodata/repomd.xml' not found on medium - info after starting apper
Comment 2 Justin Zobel 2022-11-08 06:50:19 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-23 05:13:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-08 05:13:36 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!