[Bug 325706] Re: [jaunty] Xephyr fails with D-Bus AccessDenied

[Morgan Collett]

A consequence of the D-Bus change is that "allow own" but be explicitly
specified in /etc/dbus-1/system.d/xorg-server.conf, so to run Xephyr on
:2 it must specify <allow own="org.x.config.display2"/>.

The real problem here is that Sugar runs Xephyr in its sugar-emulator
mode, on anything between :100 and :110.

I'd consider patching Sugar to run Xephyr on :1, but my jaunty
virtualbox vm seems to be running X on :0 and :1 already.

-- 
[jaunty] Xephyr fails with D-Bus AccessDenied
https://bugs.launchpad.net/bugs/325706
You received this bug notification because you are a member of Sugar
Team, which is a direct subscriber.

Status in “xorg-server” source package in Ubuntu: New

Bug description:
Running Xephyr from xserver-xephyr 2:1.5.99.902-0ubuntu1 fails with an error like:

[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.260" is not allowed to own the service "org.x.config.display2" due to security policies in the configuration file)

I suspect this is due to the recent D-Bus policy change, e.g. bug 318752.

It can be reproduced by running "Xephyr :2" in jaunty.