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 3525F138931 for ; Sat, 9 Feb 2013 09:13:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3183321C092; Sat, 9 Feb 2013 09:13:13 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id 6C52421C072 for ; Sat, 9 Feb 2013 09:13:11 +0000 (UTC) Received: from android-576d40b20a46728f.digimed.co.uk (unknown [192.168.1.133]) by mail.digimed.co.uk (Postfix) with ESMTPSA id B4ABB80147 for ; Sat, 9 Feb 2013 09:13:09 +0000 (GMT) User-Agent: K-9 Mail for Android In-Reply-To: <51159526.3000609@gmail.com> References: <51153E3C.7030707@gmail.com> <20130208194114.GA17542@dethkomp> <51156297.4010606@gmail.com> <20130208221139.5e0484d8@digimed.co.uk> <51157AFB.7040208@gmail.com> <51157FF9.1040702@gmail.com> <20130208225455.3c533d8c@digimed.co.uk> <51158BD3.5070605@gmx.de> <51159526.3000609@gmail.com> 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 Content-Type: multipart/alternative; boundary="----9BXQYR61D5K3QZ8HLSQU1VAU3V9TGP" Subject: Re: [gentoo-user] KDE 4.10 and plasma crashing From: Neil Bothwick Date: Sat, 09 Feb 2013 09:13:02 +0000 To: gentoo-user@lists.gentoo.org Message-ID: <983a9ce0-be25-4c96-a68d-02156a5a0627@email.android.com> X-Archives-Salt: a96d20c7-d945-486f-a302-fbb8d59c5b2e X-Archives-Hash: 74553635fe19b98f8e11bc4355c12fa0 ------9BXQYR61D5K3QZ8HLSQU1VAU3V9TGP Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Dale wrote: > Frank Steinmetzger wrote: > > Am 08.02.2013 23:54, schrieb Neil Bothwick: > >> On Fri, 08 Feb 2013 16:45:13 -0600, Dale wrote: > >> > >>> Well, switched to a newer gcc, same thing. Going back to KDE 4.9 > for a > >>> bit. They will have it fixed in a couple days. After all, Linux > has > >>> some of the smartest programmers there is. I'm not sure of some > users > >>> tho, myself included. ;-) > >> Changing CFLAGS and rebuilding one package is a lot less work that > a > >> complete downgrade. > > Only if you don't have a backup (which I did before upgrading, but I > can't be > > bothered with redoing the upgrade in only a few days, so I'll sit it > out with > > Awesome in the meantime). Thankfully, my netbook, which needs very > many an hour > > to build KDE, runs x86 and isn't affected. > > Yep. I rm'd the kde.keyword file and did a emerge -kuv world and down > went KDE. Took about 5 or 10 minutes. I cooked and ate supper while > the drive light blinked. > > Back to normal now. > > Thanks again. > > Dale > > :-) :-) > > -- > I am only responsible for what I said ... Not for what you understood > or how you interpreted my words! Of course I have backups, although a quick run of demerge got it back for me. But rolling back KDE, with the attendant hassles of messed up configs, only sidesteps the bug , which relates to qr-core not KDE. At least it prompted me to, belatedley, set up snapshots on my new ZFS setup, so some good came of it. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. ------9BXQYR61D5K3QZ8HLSQU1VAU3V9TGP Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
Dale <rdalek1967@gmail.com> wrote:
Frank Steinmetzger wrote:
Am 08.02.2013 23:54, schrieb Neil Bothwick:
On Fri, 08 Feb 2013 16:45:13 -0600, Dale wrote:

Well, switched to a newer gcc, same thing.  Going back to KDE 4.9 for a
bit.  They will have it fixed in a couple days.  After all, Linux has
some of the smartest programmers there is.  I'm not sure of some users
tho, myself included.  ;-) 
Changing CFLAGS and rebuilding one package is a lot less work that a
complete downgrade.
Only if you don't
have a backup (which I did before upgrading, but I can't be
bothered with redoing the upgrade in only a few days, so I'll sit it out with
Awesome in the meantime). Thankfully, my netbook, which needs very many an hour
to build KDE, runs x86 and isn't affected.

Yep.  I rm'd the kde.keyword file and did a emerge -kuv world and down
went KDE.  Took about 5 or 10 minutes.  I cooked and ate supper while
the drive light blinked.  

Back to normal now. 

Thanks again.

Dale

:-)  :-)

Of course I have backups, although a quick run of demerge got it back for me. But rolling back KDE, with the attendant hassles of messed up configs, only sidesteps the bug , which relates to qr-core not KDE.

At least it prompted me to, belatedley, set up snapshots on my new ZFS setup, so some good came of it.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity. ------9BXQYR61D5K3QZ8HLSQU1VAU3V9TGP--