Bug 7709 - GNOME Highly unstable on 550 mhz Dell Pentium III system
GNOME Highly unstable on 550 mhz Dell Pentium III system
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: gnome-core (Show other bugs)
6.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jonathan Blandford
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-12-09 16:12 EST by Jens Moller
Modified: 2013-04-02 00:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-03 13:47:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jens Moller 1999-12-09 16:12:20 EST
This system was shipped from Dell with OEM Red-Hat 6.0 pre-installed and
has been run that way for the last 2 months. Under Gnome, applications seem
to randomly 'not be presented', and there are times when I restart the
system where I log in and I don't get the GNOME image unless I hit CTRL ALT
DELETE. Icons dissapear, or simply don't work (ie. clicking on the
gnome-terminal icon doesn't create a terminal, and when this occurs,
attempting to select a terminal by right clicking on open space also
doesn't work).

It appears to be a race condition where things sometimes work, and other
times the system just hangs. I switched to KDE and have not had these
same problems. I don't have these problems on my home system (Cyrix 166+
based system with 64 Meg of ram and 8.4 Gig IDE Hard Drive).

The Dell system has 512 Meg of Ram and a SCSI 18 Gig hard drive. Its a
Pentium III system running at 550 mhz. The Dell Model # is 'Precision 610'.
There is an NVidia Video Card in the system.

We are seeing this problem on all 3 Dell systems (all identical) that we
just got.
Comment 1 Jonathan Blandford 2000-01-18 11:16:59 EST
Try upgrading to a newer version of GNOME

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