On Mon, 2007-06-18 at 02:18 -0400, Claude Jones wrote: > On Monday June 18 2007 1:29:37 am Claude Jones wrote: > > On Monday June 18 2007 1:20:52 am Kam Leo wrote: > > > Other options: runlevel 3 or previous/older kernel > > > > Didn't think of reverting the kernel - I've been in runlevel 3 for the > > better part of the day -- that's how I was able to get the other 20 updates > > run -- I'll the last kernel - I like that better than removing the nvidia > > driver > > Last kernel didn't help. I left selinux on for the first try, and it produced > a torrent of selinux errors -- that was one of the updates that seemed to go > through today -- looks like there's a problem there. Appended selinux=0 to > the boot line in grub and it came up OK the second try on the old kernel, but > all the other problems remained. I then removed the nvidia driver, but, that > didn't help either. > > I got that "libfreetype.so.6.3.15; 46620a2f is truncated" error when I was > removing the nvidia driver so I force reinstalled freetype, and that also > produced that same error, again! --------- WTF is going on with that? > > This is a good detective exercise, but I need some tips -- any PAM experts out > there - what could be going on with the pam package that it would cause > segfaults when ANY package management program tries to update it > > -- > Claude Jones > Brunswick, MD > It's most likely not a PAM problem. Have you tried `rm /var/lib/rpm/__db.00?` and doing a `rpm --rebuilddb` yet? Does the problem always happen when it is going to commit the RPM transaction? Try installing some other package, have it ignore the PAM package during that. Does the problem occur while you are installing a package using just rpm? Just a few things I can think of off the top of my head, just to help find where the problem actually is. -- Timothy Selivanow
