Bug 1703022 - Discover cannot remove application that has just been installed.
Summary: Discover cannot remove application that has just been installed.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-discover
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-25 10:16 UTC by Lukas Ruzicka
Modified: 2020-05-26 14:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 14:53:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lukas Ruzicka 2019-04-25 10:16:51 UTC
Description of problem:

Discover does not remove application that has been just installed. It reports that "Package was not found."
After restarting Discover, it works ok.

Version-Release number of selected component (if applicable):

Discover 5.15.4

How reproducible:

Always


Steps to Reproduce:
1. Open Discover
2. Install application
3. Try to remove it

Actual results:

Package not found is reported and app cannot be installed.

Expected results:

Application should be removed ok even on such conditions.


Additional info:

Comment 1 Rex Dieter 2019-04-25 13:16:42 UTC
Ideally, please report this upstream to bugs.kde.org

We have little resources to implement fixes downstream without at least their (upstream) collaboration, thanks.

Comment 2 Ben Cotton 2020-04-30 22:11:41 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2020-05-26 14:53:50 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.