wayland screen locker and security in general
matt.hoosier at gmail.com
Wed Apr 6 07:18:04 PDT 2011
2011/4/6 Michal Suchanek <hramrach at centrum.cz>
> 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
> >> >> that they are "busy" drawing and that the lock should NOT be engaged
> >> >> 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
> >> >> 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?
> >> Thanks
> >> Michal
> > 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.
It's not difficult for a D-Bus service implementation to monitor for
disconnection events by its clients. If mplayer crashes, wayland could
easily clear out the inhibition that mplayer had installed.
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wayland-devel