public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE 4.10 and plasma crashing
Date: Sat, 09 Feb 2013 09:13:02 +0000	[thread overview]
Message-ID: <983a9ce0-be25-4c96-a68d-02156a5a0627@email.android.com> (raw)
In-Reply-To: <51159526.3000609@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]

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
> 
> :-)  :-) 
> 
> -- 
> 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.

[-- Attachment #2: Type: text/html, Size: 2274 bytes --]

  reply	other threads:[~2013-02-09  9:13 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 [this message]
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
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=983a9ce0-be25-4c96-a68d-02156a5a0627@email.android.com \
    --to=neil@digimed.co.uk \
    --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