wayland screen locker and security in general
hramrach at centrum.cz
Wed Apr 6 03:09:12 PDT 2011
2011/4/6 Joakim Sindholt <bacn at zhasha.com>:
> On Wed, 2011-04-06 at 11:42 +0200, Michal Suchanek wrote:
>> 2011/4/5 Vinícius dos Santos Oliveira <vini.ipsmaker at gmail.com>:
>> >> How will apps like mplayer/vlc/browsers-playing-videos tell the compositor
>> >> that they are "busy" drawing and that the lock should NOT be engaged even
>> >> though there hasn't been any keyboard/mouse activity for long stretches? As
>> >> compared to "default" apps that just paint "im bored" over and over again,
>> >> where the idle lock should get switched on...
>> > Take a look at
>> > http://lists.freedesktop.org/archives/xdg/2009-April/010317.html
>> So is dbus absolutely required part of wayland then?
> No, but as it is a standard desktop component for IPC it seems fitting
> to use it. The specification is intentionally vague on the subject.
JFYI I have a desktop environment running completely without dbus.
That does not mean that dbus cannot or should not be used. It is just
not as standard as the two most bloated desktop environments might
make it seem. AFAICT dbus is just a replacement for a directory tree
with unix sockets under /tmp. Either is equally functional.
Also the Inhibit call is totally broken (assuming it turns of the
screensaver unlike the other calls that just simulate activity).
eg. mplayer starts to play back a movie, inhibits screensaver, and
crashes. Now screensaver never activates.
More information about the wayland-devel