Re: Safe to upgrade?
My experience is not as bad as your comments. It is true that I didn't have
KDE in August when surely Plasma 5 was really unstable. But now it is quite
stable. I experienced some crashes with KRunner, but not much more. I work all
days with KDE both for normal usage and for job-related tasks and is actually
stable. Sure there are more work for stabilization but now it is more than
usable.
I also read that the problem of suspend and resume will be fixed (if not
already is) in the Plasma 5.5 version.
Greetings.
Javier.
El Miércoles, 9 de diciembre de 2015 17:56:33 Marc Haber escribió:
> On Tue, Dec 08, 2015 at 06:56:45PM +0000, Chris Knadle wrote:
> > Marc Haber:
> > > On Tue, Dec 08, 2015 at 05:31:43PM +0000, Chris Knadle wrote:
> > >> However just within the last couple of weeks there's been a lot of work
> > >> on
> > >> the KDE5 packages and Plasma 5 is now usable.
> > >
> > > I still regularly experience plasmashell taking 100 % CPU and needing
> > > a kill + restart. This especially happens over night when the machine
> > > is idling away in the lock screen.
> >
> > Hmmm! I normally put my computer to sleep or hibernate for the night, so
> > I
> > haven't seen this -- ick. I wouldn't like to find that.
>
> Actually, the current behavior is a 100 % improvement over August's
> state of KDE plasma 5 when it was still a complete crash, needing a
> remote login+ kill X to get the machine back after it was left idling
> over night.
>
> I have not dared to suspend the machine since the KDE Plasma 5 update
> since if the current system doesn't even survive a night of idling,
> how could it possibly survive a suspend+resume cycle?
>
> > > I didn't report it yet since I use a locally compiled
> > > plasma-widget-addons with the quick launch widget backported from
> > > plasma 5.5.
> > >
> > > And the volume occasionally jumps up to 100 %, especially when one
> > > clicks on "leave" or does things in System Settings. My neighbors
> > > really love that.
> >
> > I have this "volume jumps to 100%" issue, but in my case it's a self-made
> >
> > thing -- in my ~/.bashrc I have this:
> > # Restore local ALSA mixer settings
> > /usr/sbin/alsactl --file ~/.config/asound.state restore
>
> Not in my case.
>
> Greetings
> Marc
Reply to: