On Wed, Jan 24, 2007 at 02:47:34PM -0000, Paul Smith wrote: > dpkg -S was the very first thing I did but: > ~$ dpkg -S /usr/lib/libc.so.6 > dpkg: /usr/lib/libc.so.6 not found. > > The link might have been created by some post-install script. > > Matt: which package list are you referring to? I don't have any of the > extra packages you listed installed on my box so you must be referring > to the list added in a comment by Lorenco Trichardt.
Correct; his was attached first, and if yours was there, I didn't see it until later. > Note that his error has to do with /usr/lib/libdl, while mine is related > to /usr/lib/libc.so.6. I checked and I don't have a /usr/lib/libdl.so.2 > on my system at all, so while his symptoms might be the same as my bug > (this bug), the underlying cause is not the same. I don't know whether > it's useful to open a second bug for the libdl problem or not. It is not necessary to open a separate bug; there is only one issue as far as Ubuntu is concerned (though more than one invalid configuration may trigger it). > I don't know if the Juniper Network Connect is available for download > generally, but I don't think this is the problem. The dates on the > symlinks don't match up, and I ran ldd on the executables and all of > them find /lib/libc, /lib/libm, /lib/libpthread, and /lib/libdl: What is the date on the /usr/lib/libc.so.6 symlink, and does it correspond with anything else on the system which might provide a clue about where it came from? -- - mdz -- libc6 update for Edgy fails due to sanity check https://launchpad.net/bugs/81125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
