Red Hat Bugzilla – Bug 387791
Fails to install gdm dependency nss (for libssl3.so)
Last modified: 2007-11-30 17:12:22 EST
Description of problem:
On a fresh install, it seems that anaconda failed to install the nss package
for gdm. This would provide libssl3.so, without which gdm cannot run.
Version-Release number of selected component (if applicable):
Fedora 8 initial version
Tried only once.
Right after every boot (also after firstboot), you get:
Fedora release 8 [...]
INIT: Id "x" respawing too fast, disabled for 5 minutes
gdm starts up.
I checked the 'x' entry in /etc/inittab, ran the script there with sh -x, and
finally figured out that /usr/sbin/gdm couldn't execute because it was missing
libssl3.so. "ldd" confirms this fact.
Executing "startx" as a normal user actually works sort of fine.
Oh, they joy of optical media.
A second run failed at the media check. Let me put this on hold until I can
confirm it is not due to the flaky DVD-R. (D**n, it was Verbatim! They're
supposed to work!)
Okay, with a "clean" install medium, I cannot reproduce this. I assume the bad
medium was the reason, but I forgot to check the install logs (and they're
nuked now ;->).
Sorry for the noise. -> Closed.
I am not so sure if you were not too hasty closing that.
I am seeing something similar with different packages.
Initially filed against cups as bug 388951 but closer look
seems to indicate that anaconda is at fault.
Re comment #3:
good point. But unfortunately, I had looked at all sorts of stuff, but forgot
that there was a /root/install.log. Your log file looks as if anaconda indeed
actually missed that dependency during install.
I also didn't get any error messages during install. Back in Fedora Code 4/5/6
or so, I got "cannot read soandso.foo.rpm" if there were problems with the
install medium. So perhaps there are indeed random problems within anaconda.
Just I can't reproduce. I'll try to do this behavior justice and change my bug
closure to a dupe of yours, if you don't mind. I won't be helpful in debug
anymore though, sorry.
*** This bug has been marked as a duplicate of 388951 ***
> Just I can't reproduce.
I may try later on to go through an installation exercise again
and see what will happen. Too many instances which look strangely