Bug 19451 - Errata RPM's make clean 7.0 Wksta Install unstable
Summary: Errata RPM's make clean 7.0 Wksta Install unstable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc
Version: 7.0
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-20 10:09 UTC by Need Real Name
Modified: 2016-11-24 15:04 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-10-27 16:45:06 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2000-10-20 10:09:50 UTC
Freshly installed 7.0 on a Pentium 256Mb, 10Gb ide, ZIP ide, Gforce, SB 
Life!. Standard 'Workstation' installation, running Gnome, DHCP networking.
Rocksolid, everything works, network, sound, zip, cdrom, video, X, Gnome. 
 
Downloaded the recommended Errata RPM's from RH site. Installed 
using 'rpm - Fvh'.
 
After this upgrade, the system becomes unstable (I know, vague, cant help 
it). On unpredictable times, but mostly within ten minutes after booting, 
the system becomes unstable and no new processes can be started. Every 
command in an existing xterm (like 'ls') returns an error. Switching from 
Gnome to one of the terminals (C-A-F1) shows the login prompt, but logging 
in fails with a message like 'proc 1 respawned to often, sleeping for x 
minutes'.

I reinstalled RH 7.0 several times, each time with less modifications, but 
every time after installing the updates, the thing becomes unstable. The 
same happens when i use up2date (that's how i found out), where I forced 
up2date to include the glibc RPM's.
Am running now for a few days without the errata RPM's, no problems.

An other machine (same hw. config, but TNT2 i.s.o. Gforce), installed 
using Standard 'Server' configuration, does not have these problems. 
Stable as a rock, with errata patches installed.

The downloaded RPM's check out fine when checking the MD5 signatures.


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