From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8FDA4138927 for ; Sat, 9 Feb 2013 02:47:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 64D4321C07A; Sat, 9 Feb 2013 02:47:49 +0000 (UTC) Received: from mail-gh0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A77DA21C004 for ; Sat, 9 Feb 2013 02:47:47 +0000 (UTC) Received: by mail-gh0-f182.google.com with SMTP id z15so1022566ghb.13 for ; Fri, 08 Feb 2013 18:47:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type; bh=7gqYq1S5vHhdwUr8rPcBehaUfVLU6+2WgmGz6MekcKk=; b=qoxEZ4rzF5EtZt3y41bi79Yztrabm85NzdQO4uDPiz68IBz+cZIGEn2cWB7VS6mgmp 495GAHmJ6HbSGyTxPp5Hr1g8U+UrLTf6/VDGdeduuwAWBWwOH0qU4oVmJvdPO7NKP1J2 yXk0Ht8eVmYuGmVfMVZpxca7Q01KORQkW13t+KBIeImkQm3v359kz7DTIL+XSWftaBNa KkRGf0kjER7ETycgJvyxcR6nQ34W80IpXjXAM6ZHk9osRC/2FTurNt/VjK9yRABBKo9h aJvhwnbfNS9n6F2xPFENTNH+vLtPYI7tIvDOqJFG/zIbGkTDP2UT2cOAKRpDmtfgqgK8 TLDg== X-Received: by 10.236.137.107 with SMTP id x71mr5203247yhi.2.1360378066715; Fri, 08 Feb 2013 18:47:46 -0800 (PST) Received: from [192.168.2.5] (adsl-74-240-57-140.jan.bellsouth.net. [74.240.57.140]) by mx.google.com with ESMTPS id d19sm30481310anm.18.2013.02.08.18.47.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 18:47:46 -0800 (PST) Message-ID: <5115B8D0.9070907@gmail.com> Date: Fri, 08 Feb 2013 20:47:44 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] KDE 4.10 and plasma crashing References: <51153E3C.7030707@gmail.com> <20130208194114.GA17542@dethkomp> <51156297.4010606@gmail.com> <20130208221139.5e0484d8@digimed.co.uk> <51157AFB.7040208@gmail.com> <20130209022308.GA22757@eisen.lan> In-Reply-To: <20130209022308.GA22757@eisen.lan> X-Enigmail-Version: 1.5 Content-Type: multipart/alternative; boundary="------------000806080202070709080605" X-Archives-Salt: 6470accf-65b7-463e-ba1f-f99a1aa23adc X-Archives-Hash: ff1b815796a8580c106ed843d024758c This is a multi-part message in MIME format. --------------000806080202070709080605 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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! --------------000806080202070709080605 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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!

--------------000806080202070709080605--