After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 58459 - gnorpm goes in an infinite loop in the install dialog if homedir is in install directory.
gnorpm goes in an infinite loop in the install dialog if homedir is in instal...
Status: RESOLVED FIXED
Product: gnorpm
Classification: Deprecated
Component: general
0.96
Other Linux
: Normal normal
: ---
Assigned To: Alan
Alan
Depends on:
Blocks:
 
 
Reported: 2001-08-02 18:16 UTC by Alexander Larsson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander Larsson 2001-08-02 18:16:04 UTC
Note: This bug was moved here from the Red Hat bugtracker at:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=35774

Opened by s.bach@dokom.net  2001-04-12 03:47:13

Gnorpm goes in an infinite loop in the install dialog.
It's a local install, no network involved.
He displays all found packages in the known way (tree),
but he displays all packages infinite times and doesn't stop.


Reproducible: Always
Steps to Reproduce:
1. start gnorpm
2. push the install button
	

Actual Results:  infinite loop

Expected Results:  normal display of all found packages

Additional comment by alan@redhat.com 2001-05-03 10:34:16

Which version and what CD is mounted ?

Additional comment by mkofler@tampabay.rr.com 2001-05-12 15:29:57

I'm having the same problem, using gnorpm-0.95.1.6.7x..
Hitting install does the same thing whether I'm looking to add RPMs from a
CD or
just from the hard drive.

Additional comment by jbj@redhat.com 2001-05-12 15:34:25

Can you hum a few notes about how to reproduce the problem? What packages
you're trying to install and the steps necessary to reproduce what be nice ...

Additional comment by mkofler@tampabay.rr.com 2001-05-12 16:35:40

I start GnoRPM and enter the password to su for root priveleges. Gno-RPM loads
and I click "Install". The Install screen comes up and gives the normal tree
diagram of programs to install (from the basic CD that my version of red
hat 7.0
came on, for example...although it does the same thing even if no CD is
mounted). The problem is that it keeps listing these RPMs over and over (i let
it run for a few hours one time just to see...all it did was eat system
resources and keep listing the RPMs over and over again). Even if no CD is
mounted, it does the same thing...it was giving me a list that just contained
Packages/Development/Libraries/python-xmlrpc-1.2.1-1 and Packages/System
Environment/Base/up2date-2.1.7-1 and up2date-gnome-2.1.7-1 in the default light
grey for Older Colour Packages.  
The filter Install is using is "All but installed packages"... I can't
change it
until it finishes finding packages, which it never does. 
When a Cd is mounted it seems to loop it's findings of all the packages on the
CD.
Anything else?
-M

Additional comment by mkofler@tampabay.rr.com 2001-07-24 15:50:27

Here's how to fix the problem:
Go to the Operations/Preferences menu of gnoRPM. 
Switch to the Install Window tab.
Edit the RPM directories at the bottom to just reflect the location of the 
RPMs you want to install (in our case it would have been 
/mnt/cdrom/RedHat/RPMS, and /mnt/cdrom/SRPMS if  you want the source code). 
Click Apply, then Ok. Now when you click the install button, it should work 
fine.

Additional comment by mkofler@tampabay.rr.com 2001-07-26 19:21:55

The problem seems to be the addition of the user's home directory to the 
Install Window list. If this directory is listed, gnoRPM goes into the 
infinite loop.
Comment 1 Malcolm Tredinnick 2002-04-26 02:12:36 UTC
This is now fixed in the CVS version. The problem was that GNOME 1.x
has a link from $HOME/.gnome_desktop/Home to $HOME. The directory
recursing code didn't detect loops like this and so kept on searching
pretty much forever.

I will try to make a release shortly so that bug fixes like this can
start to filter upstream.