Red Hat Bugzilla – Bug 90152
Desktop rpm installer should give feedback on failure
Last modified: 2007-04-18 12:53:27 EDT
Description of problem: If you attempt to install an rpm from the desktop and it results in an error or failure, the installer should report the error in a dialog box. Instead, it simply exits silently, forcing the user to search through log files and/or run the installer from the command line to determine what went wrong. Version-Release number of selected component (if applicable): Running the rpm installer in Red Hat 9. How reproducible: Whenever the installer exits abruptly Steps to Reproduce: 1. Attempt to install an rpm from the desktop that would cause the rpm installer to fail 2. 3. Actual results: RPM installer begins by looking at dependencies, and then the progress bar disappears and the installer disappears with no feedback. Expected results: The RPM installer should display an error message, such as the error output, to give the user some indication of what went wrong, or that something went wrong. Additional info:
If you run 'redhat-install-packages foo' from the command line, what sort of output do you get?
Running it from the command line does give some useful feedback in every case. The problem is, for the newbie user (which I was), it is quite confusing when it fails without giving any indication of why. I should note that it does give graphical feedback sometimes (i.e., when a dependency check has failed), but not at other times (if the rpm database is corrupted, and in other cases).
I'm adding feedback for the cases that are detectable as I get them... without knowing specifically where you're hitting problems, it's hard to do more. I've already got exception catching around everything I can think of.
Okay, here's an example. Attempt to install libdvdcss-1.2.6-fr2.i386.rpm, and the following comes out on the command line: redhat-install-packages libdvdcss-1.2.6-fr2.i386.rp m error: cannot open Packages database in /var/lib/rpm warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID e42d547b Traceback (most recent call last): File "/usr/share/redhat-config-packages/SinglePackageWindow.py", line 252, in ? main_window.run() File "/usr/share/redhat-config-packages/SinglePackageWindow.py", line 216, in run self.do_initial_setup () File "/usr/share/redhat-config-packages/SinglePackageWindow.py", line 145, in do_initial_setup h = ts.hdrFromFdno(fd) rpm.error: public key not available Note that the problem is NOT that the Packages database is unavailable --- running it on another package works fine. You can download this rpm here: http://rpmfind.net/linux/RPM/Shrike_Freshrpms.html Of course, this might not be the right .rpm to install on my system, but the point is that it is failing with no graphical feedback. Now that I check, it appears that this problem always happens with packages with "-fr" in the filename; does this mean they are from freshrpms? In any case, the -fr packages always seem to fail in the above way.
Mitsu, that's bug 88343.
*** This bug has been marked as a duplicate of 88343 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.