Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cannot install downloaded RPM files from *Nautilus*
The *yum* backend to *PackageKit* does not support getting details about local files. As a consequence, when an RPM file is double clicked in the *Nautilus* file manger, the file is not installed, and the following error message is returned:
Sorry, this did not work, File is not supported
To work around this problem, either install the _gnome-packagekit_ package to handle the double-click action, or manually install the files using the *yum* utility.
Created attachment 1265118[details]
error_message
Description of problem:
Gnome-software is able to open rpm, but it leads to immediate error window.
Version-Release number of selected component (if applicable):
gnome-software-3.22.7-1.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1.Download atom rpm from https://atom.io/download/rpm
2.open nautilus and open the .rpm file - or open directly via firefox
Actual results:
Error window - Sorry, this did not work, File is not supported
Expected results:
GS should open the file and install it
Additional info:
Same functionality is fully working with flatpaks
Created attachment 1288082[details]
full log
Here is an output generated after clicking the rpm, full log is attached above.
...
14:00:43:0048 As run 0x3250370~GsPlugin::packagekit-local(gs_plugin_file_to_app)
14:00:43:0048 PK role now get-details-local
14:00:43:0085 Gs emitting global waiting
14:00:43:0088 Gs emitting global querying
14:00:43:0088 Gs (null) non-transient state now local
14:00:43:0089 PK role now get-files-local
14:00:43:0104 Gs emitting global waiting
14:00:43:0108 Gs failed to call gs_plugin_file_to_app on packagekit-local: GetFilesLocal not supported by backend
14:00:43:0108 As run 0x3250370~GsPlugin::flatpak(gs_plugin_file_to_app)
14:00:43:0109 Gs not handling bundle as scope incorrect
14:00:43:0109 Gs emitting global finished
14:00:43:0116 Gs using main window
14:00:43:0122 Gs failed to convert to GsApp: no application was created for /home/mkrajnak/Downloads/atom.x86_64.rpm
14:00:43:0234 Gs plugin no longer recently active: packagekit-offline
(In reply to Martin Krajnak from comment #2)
> GetFilesLocal not supported by backend
Ahh, so yum doesn't support this. Note, in RHEL 7 we're still using yum, as in the "exec /usr/bin/yum and scrape stdout" kind of thing. I don't think we want to fix this, it would be a lot of work.
Comment 11Red Hat Bugzilla Rules Engine
2018-04-03 19:37:15 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.