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

[Milan Bouchet-Valat]

No, Sugar is not at fault for the precise problem of this report. It's
just that comments above also had errors from Sugar that could indicate
another bug.

This report is strictly about a problem with D-Bus policy that doesn't
allow org.x.config.displayXX to be owned by users because only a few XX
values are registered (notably 1). Hard to fix since we can't clutter
the config file with values until 100.

** Changed in: xorg-server (Ubuntu)
       Status: Confirmed => Triaged

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg-server (Ubuntu)
     Assignee: nirmit (nirmit-bothra) => (unassigned)

-- 
[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” package in Ubuntu: Triaged

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.