Red Hat Bugzilla – Bug 123242
Clicking on a rpm dont starts system-install-packages
Last modified: 2007-11-30 17:10:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
I like it easy and so it would be very useful when a click on a rpm
will starts system-install-packages and not the "edit file type"
dialog from gnome :)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Try to install a rpm by clicking on it
I think this bug can be considered a dupe of Bugzilla bug 119896.
system-config-packages is doing everything (in theory) that needs to
be done for gnome-vfs to notice and run it for rpms, but it's not
working for some reason.
If there's something different that needs doing here, I need to know
what it is...
For your information, a manual execution of rpm with switch (ie. rpm
-Uvh rhl-gsg-en-9-3.noarch.rmp) doesn't produce the result I had
On above example, a manual execution itself will be successful. It
completes its task (creating and copying files to the location), but
it failed to create the menu item (shortcut) on Menus.
If I double-click on an RPM I also get the "No Action Associated"
dialog. However, if I right-click on the RPM and go to "Open With" and
then to "An Application" (which is the only item in this list), both
"File Roller" and "Install Packages" appear. Picking "Install
Packages" installs the package as it should.
If you hit the "Modify" button while "Install Packages" is selected,
you can set that action as the default for RPMs. It seems we just need
to get that association made by default.
/usr/share/mime-info/gnome-vfs.keys wasn't updated to call system-
install-packages (still calls redhat-install-packages)
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
This works in later releases, such as FC5. As mentioned above, FC2 (and FC3)
are under Fedora Legacy now, and this is not a security issues. Thus, closing.