Thus spoke Klaasjan Brand <kjb@xxxxxx> on 2003-11-13 09:22:15: > On Thu, 2003-11-13 at 07:49, Jake McHenry wrote: > > > -----Original Message----- > > > From: shrike-list-admin@xxxxxxxxxx > > > [mailto:shrike-list-admin@xxxxxxxxxx] On Behalf Of Jurgen Kramer > > > Sent: Wednesday, November 12, 2003 2:30 PM > > > To: shrike-list@xxxxxxxxxx > > > Subject: Latest glibc update ruins system? > > > > > > > > > Hi, > > > > > > I've just upgraded glibc (2.3.2-27.9.6) through the up2date > > > function. After that I am no longer able to use RPM! I get > > > the following message: > > I could not login this morning on my work pc (RH9) which uses the yum > auto-update feature which only upgraded glibc last night. X and gdm > worked, but gnome-session crashed with a glib threading error... > > Downgrading glibc to the original rh9 one fixed the issue. > > -- > Klaasjan Brand <kjb@xxxxxx> > > For me rpm and bind aren't working anymore after upgrade. How do I downgrade remotely? I don't have local access to the machine -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
