issuing ldconfig causes Bus error and core dump, inhibits execution of postinst script for libgcc1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
well while i initially found fault with libgcc1, it appears the "status 135" has something to do with the fact that the postinst calls ldconfig which encounters a bus error and core dumps... issuing ldconfig on my own yields:
ldconfig -v
/lib:
libss.so.2 -> libss.so.2.0
librt.so.1 -> librt-2.5.so
libpam.so.0 -> libpam.so.0.79
libnsl.so.1 -> libnsl-2.5.so
libm.so.6 -> libm-2.5.so
libiw.so.28 -> libiw.so.28
libe2p.so.2 -> libe2p.so.2.3
libdl.so.2 -> libdl-2.5.so
libcap.so.1 -> libcap.so.1.10
libc.so.6 -> libc-2.5.so
libatm.so.1 -> libatm.so.1.0.0
libanl.so.1 -> libanl-2.5.so
libx86.so.1 -> libx86.so.1
libacl.so.1 -> libacl.so.1.1.0
/lib32:
libpam.so.0 -> libpam.so.0.79
libacl.so.1 -> libacl.so.1.1.0
librt.so.1 -> librt-2.5.so
libnsl.so.1 -> libnsl-2.5.so
libm.so.6 -> libm-2.5.so
libdl.so.2 -> libdl-2.5.so
libc.so.6 -> libc-2.5.so
libanl.so.1 -> libanl-2.5.so
/usr/lib:
Bus error (core dumped)
- this causes the postinst for libgcc1 to fail, and then dep pkgs to fail to upgrade... casuing cascading apt-get update dep problems. im running feisty w/ bi-daily apt updates (until this) on amd64
- Richard
Changed in glibc: | |
assignee: | brian-murray → nobody |
status: | Needs Info → Confirmed |
Changed in glibc: | |
status: | New → Confirmed |
well ldconfig isn't working at all. i can't understand whats going on, i havent made any chages except letting update-manager do its thing twice a day. ive tried fooling with the postinst and postrm scrips but LDCONFIG IS not working. someone please help, i've been tresting feisty for months now with no such showstoppers and i'd really like not to have to reinstall.