xdg-screensaver uses the "dcop" binary from KDE3

Bug #539590 reported by Laurent Bonnaud on 2010-03-16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xdg-utils (Ubuntu)
Nominated for Lucid by Laurent Bonnaud

Bug Description

Binary package hint: xdg-utils

Here is the problem:

$ xdg-screensaver status
/usr/bin/xdg-screensaver: line 568: dcop: command not found
ERROR: kdesktop KScreensaverIface isEnabled returned ''

The "dcop" binary still exists in Ubuntu and belongs to package kdelibs4c2a from KDE3. However I would like to run a pure KDE4 desktop therefore I purged kdelibs4c2a from my system.

There are several places where xdg-screensaver uses dcop:

$ grep -n dcop /usr/bin/xdg-screensaver
542: dcop kdesktop KScreensaverIface enable false > /dev/null
547: dcop kdesktop KScreensaverIface configure > /dev/null
552: dcop kdesktop KScreensaverIface save > /dev/null
557: dcop kdesktop KScreensaverIface lock > /dev/null
563: dcop kdesktop KScreensaverIface quit > /dev/null
568: status=`dcop kdesktop KScreensaverIface isEnabled`

ProblemType: Bug
Architecture: i386
Date: Tue Mar 16 14:50:07 2010

DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: xdg-utils 1.0.2-6.1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic-pae
SourcePackage: xdg-utils
Uname: Linux 2.6.31-20-generic-pae i686
 (polkit-gnome-authentication-agent-1:4246): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-settings-daemon:4266): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:4266): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

Those errors are still in lucid. You need to be running a KDE session to reproduce them.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments