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] Problems starting KDE
Date: Sun, 1 Jan 2012 15:30:47 +0000	[thread overview]
Message-ID: <201201011531.04502.michaelkintzios@gmail.com> (raw)
In-Reply-To: <1325429646.10079.19.camel@laptop.limeyworld>

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

On Sunday 01 Jan 2012 14:54:06 Jeff Cranmer wrote:
> On Sat, 2011-12-31 at 13:37 -0500, Jeff Cranmer wrote:
> > On Sat, 2011-12-31 at 14:59 -0200, Claudio Roberto França Pereira wrote:
> > > On Sat, Dec 31, 2011 at 13:53, Jeff Cranmer <jeff@lotussevencars.com> 
wrote:
> > > > I'm attempting to bring up a new system.  Processor is AMD Phenom
> > > > 1055, running on a Sabertooth 990FX motherboard.  Graphics card is
> > > > an NVIDIA GEForce GTX550Ti.
> 
> \After a little bit of further investigation, I discovered that the
> 
> > kdm.log file was full of old error messages.  Deleting this log file did
> > not result in a replacement file when I retried startx
> > 
> > dmesg, however, was reporting some 'invalid opcode' errors.  After
> > finding a 2-page pdf on the correct compile flags to use with and
> > amdfam10 processors (attached), I had enabled a couple of extra compile
> > flags, -mabm and -msse4a, as well as setting -march=amdfam10.
> > 
> > I've deleted the -mabm and -msse4a compile flag options from make.conf
> > and I'm now running a full recompile (emerge -Dav system, emerge -Dav
> > world).  If that doesn't work, I'll try changing the architecture flag
> > to -march=amd64 and recompile once more.
> 
> I changed to -march=k8 in the make.conf file, removed all packages from
> kde-base to trigger a meta recompile, then re-installed kde-meta and
> compiled everything else using emerge -Dav system and emerge -Dav world.
> I still get the same error.
> 
> from dmesg
> kded4[16907] trap invalid opcode ip:7fde193e74d7 sp:7fffa5120510 error:0
> in libqtGui.so.4.7.4[7fde19226000+a74000]
> kcminit_startup[16909] trap invalid opcode ip:7fde193e74d7
> sp:7fffa5120610 error:0 in libqtGui.so.4.7.4[7fde19226000+a74000]
> kcmserver[16911] trap invalid opcode ip:7fde193e74d7 sp:7fffa511ff70
> error:0 in libqtGui.so.4.7.4[7fde19226000+a74000]
> 
> So it appears that the problem is in libQtGui.so.4.7.4
> How do I know that I've recompiled this?  I suspect this is still a
> hangover from the original compile settings.
> 
> Jeff

$ qfile libQtGui.so.4.7.4
x11-libs/qt-gui (/usr/lib64/qt4/libQtGui.so.4.7.4)

Look at the date time that you built x11-libs/qt-gui (in your emerge.log, or 
use genlop) and compare with said file.
-- 
Regards,
Mick

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

  reply	other threads:[~2012-01-01 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 15:53 [gentoo-user] Problems starting KDE Jeff Cranmer
2011-12-31 16:59 ` Claudio Roberto França Pereira
2011-12-31 18:37   ` Jeff Cranmer
2012-01-01 14:54     ` Jeff Cranmer
2012-01-01 15:30       ` Mick [this message]
2012-01-01 16:13         ` Jeff Cranmer
2012-01-01 16:23           ` Peter Humphrey
2012-01-01 20:53           ` Alan McKinnon

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=201201011531.04502.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