Red Hat Bugzilla – Bug 104794
locks up during initializing
Last modified: 2015-01-07 19:06:37 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703 Description of problem: When launching gnome from the commandline (startx). Gnome fails during network, keyboard, mouse initializing. No ICONs are present in startup screen, just box outline. If I ctl-alt-backspace, the next gnome startup attempt would result i nly a blank screen. KDE finds all services and I have to use this until gnome starts up successfully. Mozilla does not work while in KDE though. Version-Release number of selected component (if applicable): gnome-libs-1.4.1.2.90-34 How reproducible: Always Steps to Reproduce: 1. log into terminal 2.run startx 3.wait for gnome to start up. (initialize) Actual Results: 1. no problem 2. computer changes to graphical mode 3. computer hangs while starting services. Expected Results: the gnome session would work properly. Additional info: Since when my computer boots up and does not think the cable to the ethernet card is plugged in. I think that me having to manually run dhclient to get connected to the Internet is not recognizing my IP address correctly for GNOME. I haven't tried it wthout running dhclient. Also mozilla locks up in KDE, which I use while gnome s down for me.
I tried to start GNOME without running dhclient at the command line. When I tried to start GNOME, it worked. I ran dhclient from a gnome-terminal and was able to connect to the Internet. However, when I tried to log out of GNOME to a terminal, it would not let me do so. The problem with GNOME not starting is related to my initial startup thinking that my ethernet cable is unplugged. (3com vortex boomerang) Is there any way to prevent GNOME from locking up on startup or closing? (Short of a properly working driver for the ethernet card)
This bug was caused by a faulty NIC card. Refer to bug # 104793 for further resolutions.
There has to be some breakout from when the IP address is not resolving on startup. Maybe adding output for the afflicted to know what process is hanging. A message box or something would make it easier to diagnose. Hopefully no one will run into a working IP that is detected by GNOME as /dev/lockup. Bug being closed as WONTFIX