[Pkg-utopia-maintainers] Bug#702474: dbus: Screensaver service seems to be absent.

[Simon McVittie]

reassign 702474 kde-workspace-bin
thanks

On 06/03/13 23:19, Boris Barbour wrote:
> After a recent upgrade (and after testing the very latest dbus suggested by reportbug),
> I can no longer lock my kde session (in particular, using the Lock/Logout widget).

This seems more likely to be caused by (or at least related to) whatever
KDE package provides screensaver functionality, which appears to be
kde-workspace-bin.

> Invoking
> 
> qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock
> 
> tells me
> 
> Service 'org.freedesktop.ScreenSaver' does not exist.
> 
> Indeed, I can't seem to find any screensaver.service in /usr/share/dbus-1/services 
> Should there be one?

A well-known bus name (something that looks like
'org.freedesktop.ScreenSaver') can be made available to D-Bus in two ways:

* an application that was run for some other reason claims that name; or

* a file in .../dbus-1/services has Name=org.freedesktop.ScreenSaver
  and Exec=some application, where that application claims the name
  when it's started ("service activation").

For a shared-between-desktops name like o.fd.ScreenSaver, .service files
aren't very useful, because if you have (say) both KDE and GNOME
installed, service-activation would choose either the KDE implementation
or the GNOME implementation, randomly. That's unlikely to make either
KDE or GNOME users happy :-)

I don't use KDE myself, but I would expect that the intended setup is
that some application or daemon that's normally run by the KDE session -
perhaps /usr/lib/kde4/libexec/kscreenlocker, or perhaps something else -
claims the name org.freedesktop.ScreenSaver when it starts up. If so,
then absence of that name means that either that daemon wasn't run for
some reason, or it was run but has crashed.

    S