public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't boot into X
Date: Thu, 17 Jun 2010 20:23:10 +0100	[thread overview]
Message-ID: <201006172023.20292.michaelkintzios@gmail.com> (raw)
In-Reply-To: <201006171854.37447.wonko@wonkology.org>

[-- Attachment #1: Type: Text/Plain, Size: 1916 bytes --]

On Thursday 17 June 2010 17:54:35 Alex Schuster wrote:
> Colleen Beamer writes:
> > First, I looked in the archives and didn't find anything relevant -
> > could be my stupidity, but I did try!
> 
> Fine :)
> 
> > From my kdm log the last few lines are as follows:
> >
> > (EE) Failed to load module "dri" (module does not exist, 0)
> > (EE) Failed to load module "dri2" (module does not exist, 0)
> 
> I have this too, when using ati-drivers. I think the nvidia-drivers also
> have their own dri, so this is okay.
> 
> > /usr/lib/kde4/libexec/kdm_greet:  error while loading shared libraries:
> > libpng12.so.0:  cannot open shared object file:  No such file or
> > directory
> 
> [...]
> 
> > Regarding libpng - on my first upgrade 6 days ago, I removed libpng
> > prior to doing the update because the updated libpng file was being
> > blocked by the existing one.  I don't know if this makes a difference.
> 
> This is the problem. /usr/lib/kde4/libexec/kdm_greet links to
> libpng12.so.0, which you removed. It needs to be rebuilt so it links
> against libpng14.so.0. A simple emerge -1 kde-base/kdm should solve this.
> Use ldd /usr/lib/kde4/libexec/kdm_greet to verify this, there should be no
> 'not found' entries.
> 
> Better use revdep-rebuild, there might be many other things that are still
> linked to the old libpng.
> 
> You could also try to emerge media-libs/libpng:1.2, this will install the
> old libpng in parallel. At least I do have both on my system, but my kdm
> inks to 1.4. If the revdep-rebuild list is very long, maybe you can get a
> working system faster this way.

 
media-libs/libpng-1.4.2 is still ~amd64 and ~x86, so there shouldn't be a need 
to emerge it at this stage.  Alex's suggestion to emerge -1aDv kde-base/kdm 
will most likely fix your problem and you can run revdep-rebuild afterwards 
for good measure.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-17 19:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 15:58 [gentoo-user] Can't boot into X Colleen Beamer
     [not found] ` <AANLkTimwf7VOv7gX5o2EBB7FX2Zft0xaJpu_Eunb9q1D@mail.gmail.com>
2010-06-17 16:39   ` Alan McKinnon
2010-06-17 16:54 ` Alex Schuster
2010-06-17 19:23   ` Mick [this message]
2010-06-18 18:34   ` Colleen Beamer
2010-06-18 19:21     ` Alex Schuster
2010-06-18 22:33       ` CJoeB
2010-06-17 18:56 ` [gentoo-user] " James
2010-06-17 19:13   ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201006172023.20292.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox