Bug 995723 - Installing a package via a web link produces an error message, but installation went fine
Summary: Installing a package via a web link produces an error message, but installati...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1007933 1030716 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-10 13:56 UTC by info@kobaltwit.be
Modified: 2017-08-08 11:43 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 11:43:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description info@kobaltwit.be 2013-08-10 13:56:05 UTC
Description of problem:
I tried configuring some extra repositories directly via a link on the internet (the links are rpm files that will set up the extra repository).

The installation itself works, but apper ends with a (bogus) error message. This is very confusing.

Version-Release number of selected component (if applicable):
apper-0.8.1-1.fc19.x86_64

How reproducible:
Always


Steps to Reproduce:
1. You probably have to start from within a kde session.
2. Go to a website that has some direct link to an rpm file to install. For example these links on rpmfusion:
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-19.noarch.rpm
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-19.noarch.rpm
3. Click the link and follow Apper's guided steps to install the rpm
4. Observe the error message in the end
5. From the command line run 'rpm -qi rpmfusion-free-release-19' (or whatever the name of the package you just installed
6. Observe that the package has been installed successfully anyway.

Actual results:
Step 3 gives this error in the end:

"Repository name was not found

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

Details:
cannot find repo local"

When the error message is dismissed, apper shows this:

"Final result: Failed to install files

Could not install files"

Yet the rpm is installed as observed in step 6

Expected results:
Successful install of the package and no error message.

Additional info:
- I'm not sure apper itself is generating this error message, rather than packagekit. I have reported against apper anyway because that's the interface I see the error message in.

- My browser is Firefox.

- I have run into this with each new repository I have added directly from the web. Apart from the rpmfusion repos, I also ran into this with Adobe's yum repository installation for flash. I'm aware none of these are Fedora controlled or endorsed, but I think this is a general problem in apper/packagekit which get confused when an rpm is installed that's not part of a repo.

Comment 1 Daniel Nicoletti 2013-08-12 19:46:50 UTC
This is an issue with the packagekit yum backend, I remmember seeing this issue before, not sure if it was fixed yet. Iirc there is an workaround.

Comment 2 Rex Dieter 2013-12-19 16:36:56 UTC
*** Bug 1007933 has been marked as a duplicate of this bug. ***

Comment 3 Rex Dieter 2013-12-19 16:37:05 UTC
*** Bug 1030716 has been marked as a duplicate of this bug. ***

Comment 4 Rex Dieter 2013-12-19 16:39:30 UTC
Confirmed, apper simply reports the error from the backend, in this case,

    case Transaction::ErrorRepoNotFound :
        return i18n("The remote software origin name was not found.\n"
                    "You may need to enable an item in Software Origins.");

and,

void PkTransaction::installFiles()
{
    setupTransaction();
    Transaction::installFiles(d->files, d->flags);
    if (internalError()) {
        showSorry(i18np("Failed to install file",
                        "Failed to install files", d->files.size()),
                  PkStrings::daemonError(internalError()));
    }
}

Comment 5 Rex Dieter 2013-12-19 16:42:28 UTC
should I just silence apper reporting these backend errors?

Comment 6 Elia Devito 2013-12-30 01:30:50 UTC
on Fedora 20 Beta I have this issue when I try to install local rpm from apper
for example (rpmfusion, mysql-workbench)

Comment 7 Wei Mu 2014-01-18 07:35:48 UTC
Additional info:
I have encountered the same bug on fedora 19.
Although the failure message "cannot find repo local" is returned,
the package is successfully installed without other problems.
Seems to be a packagekit yum backend bug.

Comment 8 Tristan Schmelcher 2014-10-13 13:26:26 UTC
This also affects installation of Google-packaged software such as Chrome. Is there a way to work around it in the package?

Comment 9 Mustafa Muhammad 2014-10-14 05:47:49 UTC
This happens in F20 too,I think we should raise its priority, I think everybody using Fedora and installs Chrome, of Flash Player, or any 3rd party rpm will face it.

Comment 10 Fedora End Of Life 2015-01-09 22:15:15 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 11 info@kobaltwit.be 2015-01-16 16:04:18 UTC
I ran the following test on Fedora 20

- use Firefox to go to Koji (http://koji.fedoraproject.org)
- search for gnucash
- on the gnucash page click on the link for the 2.6.5-1.fc20 build
- on the page that appears click on the download link after the x86_64 rpm

The download window gives me the option to use apper to install the package. That's the option I select.
When the download finishes I get a small dialog asking if I want to install the package (in Dutch: Wilt u dit bestand installeren?)
I click install.
Immediatel a second dialog pops up telling me the installation failed (in Dutch: Installeren van bestand is mislukt). Reason is an unknown error.

The package itself is successfully downloaded as /tmp/gnucash-2.6.5-1.fc20.x86_64.rpm.
And using yum localinstall I can install it without any issue.

Conclusion: this issue is not fixed in Fedora 20, so I have changed the version te keep the bug open.

Comment 12 Fedora End Of Life 2015-05-29 09:18:31 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 13 Mustafa Muhammad 2015-06-01 21:43:47 UTC
Still affecting Apper in F22

Comment 14 info@kobaltwit.be 2015-06-02 06:53:50 UTC
Tested F21 today as well. Not fixed either. I'll bump the version to 22.

Comment 15 David Tonhofer 2015-12-26 15:40:30 UTC
Same problem in Fedora 23 (?)

1) Go to http://rpmfusion.org/Configuration 
2) Click on the "free" link for "rpmfusion free repositories"

The link will start "apper" and configure the repositories (asks for root password).

The Apper starts to download the remote repository. This takes a bit. Then the operation breaks off with:

>> Failed to find rpmfusion-free-release:23-0.1;noarch;local"

Those semicolons are very fishy...

The package "rpmfusion-free-release-23.0.1.noarch" actually has been installed ok.

Comment 16 Kevin Kofler 2016-02-02 03:24:16 UTC
Bumping as per comment #15.

Comment 17 Fedora End Of Life 2016-11-24 11:01:26 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 18 Fedora End Of Life 2016-12-20 12:40:59 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Comment 19 Kevin Kofler 2016-12-20 13:16:10 UTC
This is still current with the Apper in F24, at least. I'll have to recheck with F25/Rawhide.

Comment 20 Fedora End Of Life 2017-07-25 18:34:21 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 21 Fedora End Of Life 2017-08-08 11:43:03 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.