Bug 505082 - upgrade from F10 to F11 leaves unresolved library reference, login fails
upgrade from F10 to F11 leaves unresolved library reference, login fails
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: glibc (Show other bugs)
11
All Linux
low Severity medium
: ---
: ---
Assigned To: Andreas Schwab
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-10 11:40 EDT by John Dennis
Modified: 2009-11-22 21:38 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-11-22 21:38:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Dennis 2009-06-10 11:40:41 EDT
After upgrading an F10 installation to F11 I was unable to login due to an unresolved library. The login process emits the following loader error:

lib/ld_linux.so.2 not found, required by /lib/libc.so.6

boot into single user mode and running ldconfig resolved the problem. Not sure who is responsible for not running ldconfig, the package owning the library or the installer after all packages were upgraded.
Comment 1 Chris Lumens 2009-06-10 11:43:57 EDT
ldconfig is usually run out of the package's post-install scriptlet.
Comment 2 John Dennis 2009-06-10 11:52:08 EDT
both /lib/lid-linux.so.2 and /lib/libc.so.6 are owned by glibc, reassigning component.
Comment 3 Ulrich Drepper 2009-11-22 21:38:02 EST
(In reply to comment #0)
> After upgrading an F10 installation to F11 I was unable to login due to an
> unresolved library. The login process emits the following loader error:
> 
> lib/ld_linux.so.2 not found, required by /lib/libc.so.6

This cannot have been the real message.  There is at least one typo it in, likely two.  Was there an initial / or not?  And ld_linux must have been ld-linux.


> boot into single user mode and running ldconfig resolved the problem. Not sure
> who is responsible for not running ldconfig, the package owning the library or
> the installer after all packages were upgraded.  

The only possibility I see is that during the glibc installation ldconfig failed to run.  Some problem in the post-install code or so.  But there haven't been any other reports.  Perhaps your system wasn't clean.  And the /lib/ld-linux.so.2 links better be there since otherwise apps won't start at all (or is this a 64-bit machine).

Anyway, this is not a problem with the code, at most with the installation.  Nobody has been able to reproduce it so I close it.  If there is a reproducer, reopen.

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