[Bug 291381] Random black screenlocker
Lamarque V. Souza
lamarque at kde.org
Tue Apr 24 19:28:31 UTC 2012
--- Comment #8 from Lamarque V. Souza <lamarque at kde.org> ---
(In reply to comment #7)
> pot. either driver bug or utilization of MSAA and no glClearColor in the
> screensaver hack - see bug #263974
Ok, I do not understand much about OpenGL programming. Where the hack you are
talking about is located? In kwin or in the screensavers?
> There's been some talk on screensavers, Martin actually wanted to move it to
> kwin, but there've been opposing statements. My personally favorite location
> would actually be kdm and invoke a kdm greeter as security layer.
> See http://lists.kde.org/?t=131818348300001&r=1&w=2 for the k-c-d thread and
> -self promoting-
> http://lists.kde.org/?l=kde-core-devel&m=131853544901721&w=2 for ossis talk
> on kdm usage
I followed some of those discussions. Well, it seems there are people
interested in using light-dm instead of kdm, how that would affect moving
screenlocker to kdm? What about this approach to move it to ksmserver? If the
locker crashes the user is just logged off, there is less security risk, just
the possible data loss is the problem :-) Specialy if you use one of those
crazy optimizations filesystems use to make them look good in benchmarks.
You are receiving this mail because:
You are the assignee for the bug.
More information about the Active