From: Nilesh Govindrajan <me@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE 4.10 and plasma crashing
Date: Sat, 09 Feb 2013 09:58:57 +0530 [thread overview]
Message-ID: <5115D089.8050701@nileshgr.com> (raw)
In-Reply-To: <5115B8D0.9070907@gmail.com>
On Saturday 09 February 2013 08:17:44 AM IST, Dale wrote:
> Frank Steinmetzger wrote:
> > On Fri, Feb 08, 2013 at 04:23:55PM -0600, Dale wrote:
> >> Neil Bothwick wrote:
> >>> On Fri, 08 Feb 2013 14:39:51 -0600, Dale wrote:
> >>>
> >>>> Mike posted a bug number. I guess it doesn't hit everyone but it did
> >>>> me. Is anyone that knows me surprised that this bug hit me? :-)
> >>>
> >>> If affected my laptop but not my desktop. Re-emerging qt-core with
> >>> -Os in CFLAGS instead of -O2 "fixes" it.
> >>
> >> I think I am going to go back to KDE 4.9 for now. They are working on
> >> it. It appears that gcc is the real problem tho. So, I may just
> >> upgrade it and see what it breaks. lol Come to think of it, I may
> >> already have a newer one installed. Its been a while since I switched
> >> gcc versions. Hmmm, going to test this. ;-)
> >
> > I just went the least way of resistance and built qt-core with -Os.
> It solved
> > the problem for me, too¹.
> >
> > Even if my machine had the power to emerge -eD world, that doesn’t
> mean I
> > should do this all the time, just because it might solve a problem
> (with a big
> > MIGHT). Electricity isn’t as clean as in Captain Picard’s days just
> yet. ;-)
> >
> > ¹ had -O2 as well, latest stable gcc 4.6.3
>
> Actually, according to the bug report, that may not fix it for
> everyone. So, there is a chance that may not work. The thinking was
> it was something to do with gcc. Then someone posted that it wasn't
> gcc but something else. I just don't want to use something that I
> know has issues and *could* cause problems I am not aware of.
>
> My easy way to to remove the package.keyword file for KDE 4.10 and
> just emerge -uvk world. I keep binaries just for when this sort of
> things happens. It's been a good long while since this has happenend
> with a KDE upgrade but I'm glad I had them. 5 to 10 minutes and I am
> back to a working system. The devs will have this fixed in the next
> couple days if it is not fixed upstream already.
>
> Dale
>
> :-) :-)
>
> --
> I am only responsible for what I said ... Not for what you understood
> or how you interpreted my words!
>
Dale, which version of GCC are you using? I'm on 4.7.2, updating KDE
now, will report back after a few hours when it's done.
--
Nilesh Govindarajan
http://nileshgr.com
next prev parent reply other threads:[~2013-02-09 4:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 18:04 [gentoo-user] KDE 4.10 and plasma crashing Dale
2013-02-08 18:18 ` Nilesh Govindrajan
2013-02-08 18:55 ` Dale
2013-02-08 18:59 ` Nilesh Govindrajan
2013-02-08 19:39 ` Dale
2013-02-08 20:07 ` Mike Gilbert
2013-02-08 19:41 ` Yohan Pereira
2013-02-08 20:39 ` Dale
2013-02-08 22:11 ` Neil Bothwick
2013-02-08 22:23 ` Dale
2013-02-08 22:45 ` Dale
2013-02-08 22:54 ` Neil Bothwick
2013-02-08 23:35 ` Frank Steinmetzger
2013-02-09 0:15 ` Dale
2013-02-09 9:13 ` Neil Bothwick
2013-02-09 16:25 ` Dale
2013-02-10 10:22 ` Neil Bothwick
2013-02-10 12:08 ` Robin Atwood
2013-02-10 15:59 ` Dale
2013-02-09 2:23 ` Frank Steinmetzger
2013-02-09 2:47 ` Dale
2013-02-09 4:28 ` Nilesh Govindrajan [this message]
2013-02-09 12:40 ` Nilesh Govindrajan
2013-02-10 6:12 ` 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=5115D089.8050701@nileshgr.com \
--to=me@nileshgr.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