public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE 4.10 and plasma crashing
Date: Sun, 10 Feb 2013 09:59:40 -0600	[thread overview]
Message-ID: <5117C3EC.1000308@gmail.com> (raw)
In-Reply-To: <201302102008.26369.robin.atwood@attglobal.net>

Robin Atwood wrote:
> On Sunday 10 Feb 2013, Neil Bothwick wrote:
>> On Sat, 09 Feb 2013 10:25:25 -0600, Dale wrote:
>>>> 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.
>>> I didn't have any config problems at all.  I did have to update but its
>>> the same thing I have to do when I do a upgrade.
>> It's not the same. KDE has an inbuilt system for handling upgrades, one
>> that does any config file conversions that may be needed without the
>> applications needing to worry about it. But it only handles upgrades, not
>> downgrades. After downgrading, my Activities were messed up.
>>
>> Of course, the best thing about tackling the problem at, or at least
>> nearer, the source is that I won't have to upgrade KDE again when it's
>> fixed ;-)
> The issue is now moot, if you sync and upgrade you will get a new qt-core and 
> plasma-workspace which work happily when compiled with -O2. :)
>
> -Robin

That's good to hear Robin.  I knew they would get it fixed, as soon as
they nailed jello to the wall and figured out what was broke.  lol 

I guess I keep my KDE to simple then Neil.  I went backwards and other
than the fact everything worked, I couldn't tell any difference.  I
don't think I use "activities" so maybe I need to check into those.  If
I start using those, that will be something else I can watch for
breakage on.  ;-)  lol

Plan to upgrade later tonight.  Sort of let the tree settle a bit. 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!



  reply	other threads:[~2013-02-10 15:59 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 [this message]
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=5117C3EC.1000308@gmail.com \
    --to=rdalek1967@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