contact at nileshgr
Apr 22, 2012, 8:32 PM
Post #3 of 3
On Mon, Apr 23, 2012 at 8:29 AM, <kwkhui [at] hkbn> wrote:
Re: Not able to login as root after update
[In reply to]
> On Mon, 23 Apr 2012 07:17:45 +0530
> Nilesh Govindrajan <contact [at] nileshgr> wrote:
>> There's some weird problem that has cropped up after update yesterday.
>> I'm not able to login as root on the tty nor as su -l and neither
>> using sudo su -l. Thankfully I had sudo, so I can get root by sudo -i,
>> or else it would've been a complete disaster.
>> The packages which were upgraded yesterday which can be causing this
>> is pambase, shadow and glibc.
>> Anybody has idea how to fix this?
>> (PS: I know very well that logging in as root is a bad practice and I
>> never do that, I just use su -l, so no flames please).
> If you mean shadow-4.1.5-r1 and pambase-20120417, read the previous
> pambase/shadow warning thread from 3 days ago, or bug #412721, or you
> can read it on phajdan.jr's blog
> Anyway, if you upgrade glibc, you must recompile pam
> afterwards manually (sorry it wasn't clear if you recompiled pam after
> glibc upgrade) since it uses dlopen() which isn't catched by
> revdep-rebuild. Safest is to recompile the toolchain, then system, then
> world, but that could take a long time.
When glibc comes with @world updates, emerge usually merges glibc
first and then the rest.
Ugh, I'd run the update command inside tmux and this issue caused me
not to check tmux after update. Running dispatch-conf fixed it,