Red Hat Bugzilla – Bug 78830
gnome2-info2html infinite loop when started from redhat-config-network
Last modified: 2007-04-18 12:48:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
When trying to get help in redhat-config-network, I get the index for "Network
Configuration", but I hang after selecting a topic. It appears that
gnome2-info2html goes into an infinite loop.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start redhat-config-network in any fashion.
2.Click on "Help"
3.Click on "Introduction" or "Overview".
Actual Results: Yelp puts up a "Loading" window waiting for gnome2-info2html to
finish, but it never does.
Expected Results: The chosen topic should come back pretty fast as I am running
on a dual CPU Athlon system with lots of memory and disk space.
This may not be related. When I click on Help in redhat-config-network, I get
the following messages:
(neat:2207): Gnome-CRITICAL **: file gnome-program.c: line 738
(gnome_program_get_app_id): assertion `program != NULL' failed
(neat:2207): GConf-CRITICAL **: file gconf-client.c: line 545
(gconf_client_add_dir): assertion `gconf_valid_key (dirname, NULL)' failed
Confirming - I also see this problem.
$ rpm -q redhat-config-network
This priority should be upgraded to HIGH. Its severity rating might also need
to be upgraded since it can render a machine slow without any means of
correcting it (without manually finding and killing the gnome2-info2html
process). The component may need to be switched to libgnome since the race
condition should also be detected by gnome2-info2html.
Reason? Since redhat-config-network runs as root, gnome2-info2html also gets
spawned with root privileges and will consume almost all CPU until a super-user
kill ends the process. Killing redhat-config-network will not perpetuate a
SIGTERM down to gnome2-info2html.
This is executed:
Assigning to yelp
It looks like neat has to call gnome_program_init for show_url to work.
This is not a workaround (except for su'ers), but I think it is interesting to
note that if I kill -9 the gnome2-info2html process, then the Help Browser does
come back, and does show the intended page.
I do think the priority or severity of this bug should be increased. Imagine my
chagrin this morning to find that our webserver has been spending most of its
cycles navel gazing instead of cycling pages. It's probably been doing that for
a day or so now. Yeah, I don't have enough resources for a dedicated sysadmin.
I suspect that's a good chunk of your market.
even does not work if gnome_program_init was called before...
why is info2html called?? these pages are already in html???
harald: I'm not sure what you mean here. In the latest beta, when i click on
help in r-c-network i get a mozilla window, not yelp.
*** Bug 80236 has been marked as a duplicate of this bug. ***
This has been changed to use the web browser instead of yelp and works
fine in current release.