Bug 326569

Summary: Indicates failure after installing from web browser
Product: [Unmaintained] apper Reporter: Emmett Culley <lst_manage>
Component: generalAssignee: Daniel Nicoletti <dantti12>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: 0.8.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Emmett Culley 2013-10-24 15:24:35 UTC
Each time I attempt to install a packege via Firefox, or Chrome,7 I see a popup with this text:

The remote software origin name was not found.
You may need to enable an item in Software Origins

Then when clicking on OK I see a new dialog with "Failed to install files".  However the package did get installed.  

At first I thought it was because I was installing a new repo, but this time I was installing a normal package.

Reproducible: Always

Steps to Reproduce:
1. Click on RPM package download button
2. Select to run apper against download
3. Follow popups, i.e. enter root password, agree to install regardless of unrecognized source, etc.
4. See "origin" message (above)
5. See "Failed to install files" dialog.
6. After clicking on OK in above dialog, package is installed.
Actual Results:  
Downloaded package installed even though app warns of failure.

Expected Results:  
No warning dialogs.

This has happend each time I have downloaded a package and passed it to apper, via a browser, since the OS (Fedora 19) was installed fresh.
Comment 1 Andrew Crouthamel 2018-11-10 03:21:48 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:21:00 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-02 07:43:48 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 4 Emmett Culley 2023-01-02 18:30:35 UTC
Wow.  This is old.  I don't even remember what I was doing with firefox or chrome, and don't know what it meant by "apper".

So I suppose this should be closed.
Comment 5 Bug Janitor Service 2023-01-17 05:16:16 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 6 Emmett Culley 2023-01-17 15:59:38 UTC
I have nothing to add.  This was a long timae ago, and I rarily, if ever, install from my browser, and instead use dnf exclusively.
Comment 7 Bug Janitor Service 2023-02-01 05:03:08 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 8 Bug Janitor Service 2023-02-16 03:48:30 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!