Bug 80301 - Red Hat 7.3 GnoRPM freezes on web find
Red Hat 7.3 GnoRPM freezes on web find
Product: Red Hat Linux
Classification: Retired
Component: gnorpm (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-12-24 04:21 EST by David Depin
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-24 13:17:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Depin 2002-12-24 04:21:53 EST
Description of problem:
I have installed about two days ago. I have installed packages off of cd and off
of hard drive. When I click on web find, i search for a package, it appears as a
folder. i double click on the folder to show the package, then i click on the
package. Once i click on the package, everything freezes. I can still move the
mouse and turn on and off Num Lock, but the machine accepts no commands...
making me do hard reset. how do i go about fixing this??? all my installed
packages are up to date. thank you.

Version-Release number of selected component (if applicable):

How reproducible:
Everytime on my machine.

Steps to Reproduce:
1.Go into GnoRPM
2.Goto web find
3.Select a package
Actual results:
Application locks up computer.

Expected results:
Information should be displayed about package, and package should be able to be

Additional info:
Comment 1 Havoc Pennington 2002-12-24 13:17:03 EST
It's probably just a stuck X grab - Ctrl+Alt+F1 to a virtual console, and 
run "killall -9 gnorpm" from there, may fix it. Or ssh in from another machine 
and do the killall, or worst-case only kill X with Ctrl+Alt+Backspace.

gnorpm is no longer present in 8.0 precisely because it was very buggy, 
we aren't releasing further updates for it at this point.

Note You need to log in before you can comment on or make changes to this bug.