Description of problem:
glibc's new ld.so.conf is installed as ld.so.conf.rpmnew and contains
"include ld.so.conf.d/*" however ld.so.conf.d is empty. Manifests
itself as failure to start X. Is this new ld.so.conf.d stuff supposed
to be getting filled in by package installs?
Note that if I had ignored the ld.so.conf.rpmnew, things would have
kept working -- until some package install added a file to ld.so.conf.d.
Version-Release number of selected component (if applicable):
glibc-2.3.3-18
How reproducible:
upgrade from FC1 to FC2-test2
Steps to Reproduce:
1. Do an upgrade installation of FC2-test2
2. Read thru /root/upgrade.log and notice warning about ld.so.conf.rpmnew
3. mv ld.so.conf.rpmnew to ld.so.conf
4. rerun ldconfig
5. reboot and try to startx.
Actual results:
Expected results:
Additional info:

Well, there is a problem in FC2 glibc in that it doesn't edit
/etc/ld.so.conf in glibc_post_upgrade to insert the include ld.so.conf.d/*.
So for FC2 you need to insert that manually.
Step 3. is a user bug though, if there is a rpmnew file, the administrator
is supposed to merge the files together, not simply overwrite one with
another, there might be bad consequences of doing that.
FC3t2 glibc_post_upgrade inserts include ld.so.conf.d/*, so this bug is issue
is fixed in rawhide.

Note

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