[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: [KDE4] what component does the screenlocking?
From: Luca Beltrame <lbeltrame () kde ! org>
Date: 2017-02-28 17:22:56
Message-ID: 16539547.CDH3VPsefj () giskard ! marionegri ! it
[Download RAW message or body]
In data martedì 28 febbraio 2017 18:08:40 CET, René J.V. Bertin ha scritto:
> Yeah, I know that KDE no longer maintains most of KDE4. Fortunately some
> distributions have a slightly different take on concepts like continuity
I would like if you stopped doing such blanket statements. Plasma 4 *was* on
Long Term Support for quite a while when Plasma 5 was born and for some
releases along the way.
In openSUSE we dropped Plasma 4 because continuity means *nothing* if no one
can fix bugs.
> bleeding-edge distros like KaOS fail to convince me that the "better
> Plasma5" is not indeed the enemy of "good old Plasma4", to paraphrase an
Again, blanket statement. How many distros have deployad Plasma 5 so far?
Basically most of the larger ones. In openSUSE we even put Plasma master under
openQA. n = 1 does not make a great sample size.
> If the screensaver also provides session locking I'll start with making it a
> habit to restart Plasma each time I get the screensaver glitch.
It does, and IIRC the later 4.x versions also worked like that. Technically
there's no screensaver, just a screen locker (the *community* on a KDE
Community Forums poll decided that the interest in keeping screensavers was
minimal).
> open session. If sddm supports something similar I might adopt it earlier
> than Plasma5 (presuming sddm supports other session types than Plasma5
That's why I say blanket statements are *bad*. SDDM is not made by KDE and it
does support different sessions.
--
Luca Beltrame - KDE Forums team
KDE Science supporter
GPG key ID: A29D259B
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic