Originally posted by mgraesslin
View Post
KScreensaver, KRandR Dropped From KDE Workspaces
Collapse
X
-
Originally posted by Alex Sarmiento View PostA la screensaver? i really like the fact that i can use a large monitor as a 10-foot interface dashboard to display useful information whilst not using the computer directly.
Comment
-
-
Originally posted by mgraesslin View Postit's QtQuick2 - so we plan to have the possibility of Plasma applets there.
Comment
-
-
Originally posted by schmalzler View Post
Comment
-
-
Since Wayland will not be mainstream for another 2 to 5 years why get rid of the X Screensaver code? Xorg will still be on the desktop for the next 10 years. Will there be a way to control X screensavers under KDE? I loved the KDE frontend/control of XScreensaver it was the best I used.
So please tell how will one use KDE 5 with Xscreensaver?
Comment
-
-
Originally posted by Rallos Zek View PostSince Wayland will not be mainstream for another 2 to 5 years why get rid of the X Screensaver code? Xorg will still be on the desktop for the next 10 years. Will there be a way to control X screensavers under KDE? I loved the KDE frontend/control of XScreensaver it was the best I used.
So please tell how will one use KDE 5 with Xscreensaver?
Comment
-
-
Originally posted by TheBlackCat View PostXscreensaver is inherently insecure. If my understanding is correct, kwin has moved the lockscreen into the compositor when compositing is enabled even in the KDE 4 series. This is much more secure. The xscreensaver implementation was deprecated and only used when there is no way to use compositing. I think for kwin for frameworks 5 compositing will be enforced, so there is no longer any reason to keep using the insecure Xscreensaver.
Comment
-
-
Originally posted by TheBlackCat View PostIf my understanding is correct, kwin has moved the lockscreen into the compositor when compositing is enabled even in the KDE 4 series. (...) I think for kwin for frameworks 5 compositing will be enforced
Comment
-
-
Originally posted by mgraesslin View Postno and no (random text to make this forum software happy)
Some might have already read about it: we are currently working on a new screen locker. The old implementation is mostly a hack around X. There is the lock window which tries really hard to be the …
"We decided to change that and solve it once and for all in a proper way by putting security first and moving the screen locker into the Compositor."
One of the most often repeated misconceptions about Wayland is that it requires hardware acceleration. I would have thought that this issues would have been resolved once the reference compositor, …
"Given that we have to enforce compositing in future, it’s good to know that all backends work."
Would it be possible to clarify exactly what is going on?
Comment
-
-
Originally posted by TheBlackCat View PostI am confused, isn't that what this says:
Some might have already read about it: we are currently working on a new screen locker. The old implementation is mostly a hack around X. There is the lock window which tries really hard to be the …
"We decided to change that and solve it once and for all in a proper way by putting security first and moving the screen locker into the Compositor."
Originally posted by TheBlackCat View PostOne of the most often repeated misconceptions about Wayland is that it requires hardware acceleration. I would have thought that this issues would have been resolved once the reference compositor, …
"Given that we have to enforce compositing in future, it?s good to know that all backends work."
Would it be possible to clarify exactly what is going on?
Comment
-
Comment