[jaunty] Xephyr fails with D-Bus AccessDenied

Bug #325706 reported by Morgan Collett on 2009-02-05
66
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Sugar
Invalid
Undecided
Unassigned
xorg-server (Ubuntu)
Low
Unassigned

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.

Morgan Collett (morgan) wrote :

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.

Bryce Harrington (bryce) wrote :

Not enough information to troubleshoot this issue. Make sure to at least attach an Xorg.0.log and the output of lspci -vvnn when reporting X bugs. This bug report also needs to have detailed steps to reproduce the issue.

Morgan Collett (morgan) wrote :

I can't reproduce any more, it must have been fixed along the way. Thanks

Changed in xorg-server:
status: New → Invalid
Milan Bouchet-Valat (nalimilan) wrote :

This bug is not fixed, I've just bumped on it, and there's at least one duplicate. There's an Xorg.0.log on the duplicate, but I don't see how that can be helpful.

There's obviously a D-Bus rules problem here.

Changed in xorg-server:
status: Invalid → Confirmed
Frank (frank-schaeffer) wrote :

Same here. The symptom are the same as described here and on bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/335253.

Frank (frank-schaeffer) wrote :

Xorg.0.log
Let me know if I could provide more information.

nirmit (nirmit-bothra) on 2009-03-26
Changed in xorg-server:
status: Confirmed → Fix Committed
status: Fix Committed → Confirmed
nirmit (nirmit-bothra) on 2009-03-26
Changed in xorg-server:
assignee: nobody → nirmit-bothra
status: Confirmed → Fix Committed
Milan Bouchet-Valat (nalimilan) wrote :

The problem with this bug is that X.org buses are dynamically created with numbered names. Thus you cannot specify them in a static conf as most buses. Is there an option to allow a range of buses to be created and owned?

Andrew Somerville (andy16666) wrote :

Anyone know when the fix will be available as an update?

Rob Frohne (frohro) wrote :

This happens when you try to run sugar-emulator which probably uses Xephr. I still have the problem with an updated system on 6/30/2009.

Rob

Rob Frohne (frohro) wrote :

I added what I thought were the appropriate lines to
so it looks like this now:

<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
        <policy context="default">
                <allow own="org.x.config.display0"/>
                <allow send_destination="org.x.config.display0"/>
                <allow send_interface="org.x.config.display0"/>
                <allow own="org.x.config.display1"/>
                <allow send_destination="org.x.config.display1"/>
                <allow send_interface="org.x.config.display1"/>
                <allow own="org.x.config.display100"/>
                <allow own="org.x.config.display101"/>
                <allow own="org.x.config.display102"/>
                <allow own="org.x.config.display103"/>
                <allow own="org.x.config.display104"/>
                <allow own="org.x.config.display105"/>
                <allow own="org.x.config.display106"/>
                <allow own="org.x.config.display107"/>
                <allow own="org.x.config.display108"/>
                <allow own="org.x.config.display109"/>
                <allow own="org.x.config.display110"/>
        </policy>
</busconfig>

but now I still have the following problem with sugar-emulator.

araya@araya-d600:~$ sugar-emulator
/usr/share/themes/EdubuntuColors/gtk-2.0/gtkrc:77: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
(EE) XKB: No components provided for device Virtual core keyboard
[config/dbus] couldn't register object path
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <Alt>return=fullscreen

/usr/lib/python2.6/dist-packages/jarabe/desktop/meshbox.py:19: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
/usr/lib/python2.6/dist-packages/jarabe/desktop/keydialog.py:17: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
araya@araya-d600:~$

I don't know if I should file another bug report or what. Advice solicited.

Thanks,

Rob

I'm not sure were the real problem happens in your log. The (EE) messages are not fatal IIRC, I've been seeing them in working environments. But please report this separately, I'd even expect it to be specific to Sugar.

On Wed, Jul 1, 2009 at 11:08, Milan Bouchet-Valat<email address hidden> wrote:
> I'm not sure were the real problem happens in your log. The (EE)
> messages are not fatal IIRC, I've been seeing them in working
> environments. But please report this separately, I'd even expect it to
> be specific to Sugar.

May be very well, the file ~/.sugar/default/logs/shell.log should tell.

Regards,

Tomeu

> --
> [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: Fix Committed
>
> 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.
>
> --
> Ubuntu-sugarteam mailing list
> <email address hidden>
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-sugarteam
>

Thomas C Gilliard (satellit-) wrote :

I tried to fix permissions on 9.04 sugar-emulator per notes in wiki.
still got black screen with arrow cursor. No sugar.

[xxxx]-robert:~$ sudo chown -R robert ~/.sugar
[sudo] password for robert:
[xxxx]-robert:~$ sugar-emulator
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.258" is not allowed to own the service "org.x.config.display100" due to security policies in the configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
(EE) XKB: No components provided for device Virtual core keyboard
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.258" is not allowed to own the service "org.x.config.display100" due to security policies in the configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <Alt>return=fullscreen

/usr/lib/python2.6/dist-packages/jarabe/desktop/meshbox.py:19: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
/usr/lib/python2.6/dist-packages/jarabe/desktop/keydialog.py:17: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
[xxxxx]:~$ XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 124 requests (124 known processed) with 0 events remaining.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":100.0"
      after 502 requests (502 known processed) with 0 events remaining.

Thomas C Gilliard (satellit-) wrote :

"May be very well, the file ~/.sugar/default/logs/shell.log should tell.
Regards,
Tomeu"

Here is this log for the comment above:

Tom Gilliard
satellit

** (sugar-session:28248): DEBUG: starting phase 1

** (sugar-session:28248): DEBUG: ending phase 1

** (sugar-session:28248): DEBUG: starting phase 2

** (sugar-session:28248): DEBUG: ending phase 2

** (sugar-session:28248): DEBUG: starting phase 3

** (sugar-session:28248): DEBUG: ending phase 3

** (sugar-session:28248): DEBUG: starting phase 4

** (sugar-session:28248): DEBUG: ending phase 4

** (sugar-session:28248): DEBUG: starting phase 5

** (sugar-session:28248): DEBUG: ending phase 5

Traceback (most recent call last):
  File "/usr/bin/sugar-session", line 173, in <module>
    main()
  File "/usr/bin/sugar-session", line 157, in main
    home_window = HomeWindow()
  File "/usr/lib/python2.6/dist-packages/jarabe/desktop/homewindow.py", line 55, in __init__
    self._home_box = HomeBox()
  File "/usr/lib/python2.6/dist-packages/jarabe/desktop/homebox.py", line 47, in __init__
    self._favorites_view = favoritesview.FavoritesView()
  File "/usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py", line 114, in __init__
    self._set_layout(favorites_settings.layout)
  File "/usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py", line 284, in _set_layout
    raise ValueError('Unknown favorites layout: %r' % layout)
ValueError: Unknown favorites layout: None

Looks like a Sugar problem to me, since the errors come from Python, not Xephyr. Please open a new report.

Tomeu Vizoso (tomeu) wrote :

On Wed, Jul 1, 2009 at 21:36, satellit<email address hidden> wrote:
> "May be very well, the file ~/.sugar/default/logs/shell.log should tell.
> Regards,
> Tomeu"
>
> Here is this log for the comment above:
>
> Tom Gilliard
> satellit
>
> ** (sugar-session:28248): DEBUG: starting phase 1
>
> ** (sugar-session:28248): DEBUG: ending phase 1
>
> ** (sugar-session:28248): DEBUG: starting phase 2
>
> ** (sugar-session:28248): DEBUG: ending phase 2
>
> ** (sugar-session:28248): DEBUG: starting phase 3
>
> ** (sugar-session:28248): DEBUG: ending phase 3
>
> ** (sugar-session:28248): DEBUG: starting phase 4
>
> ** (sugar-session:28248): DEBUG: ending phase 4
>
> ** (sugar-session:28248): DEBUG: starting phase 5
>
> ** (sugar-session:28248): DEBUG: ending phase 5
>
> Traceback (most recent call last):
>  File "/usr/bin/sugar-session", line 173, in <module>
>    main()
>  File "/usr/bin/sugar-session", line 157, in main
>    home_window = HomeWindow()
>  File "/usr/lib/python2.6/dist-packages/jarabe/desktop/homewindow.py", line 55, in __init__
>    self._home_box = HomeBox()
>  File "/usr/lib/python2.6/dist-packages/jarabe/desktop/homebox.py", line 47, in __init__
>    self._favorites_view = favoritesview.FavoritesView()
>  File "/usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py", line 114, in __init__
>    self._set_layout(favorites_settings.layout)
>  File "/usr/lib/python2.6/dist-packages/jarabe/desktop/favoritesview.py", line 284, in _set_layout
>    raise ValueError('Unknown favorites layout: %r' % layout)
> ValueError: Unknown favorites layout: None

This sounds to me as the GConf defaults not being installed properly.
Maybe we have already a ticket about it? I would think that the 0.84
packages from debian has this fixed.

Regards,

Tomeu

> --
> [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: Fix Committed
>
> 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.
>
> --
> Ubuntu-sugarteam mailing list
> <email address hidden>
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-sugarteam
>

Neil Mayhew (neil.mayhew) wrote :

I can confirm that running the following command once enables sugar-emulator to work, so this is NOT a Xephyr problem:

gconftool-2 -s /desktop/sugar/desktop/favorites_layout -t string ring-layout

I will file a new bug against the sugar package, or add this information to an existing bug.

Timo Aaltonen (tjaalton) wrote :

nirmit: how is this bug "fix committed"? I haven't seen any patches posted here. One way to fix it would be to disable dbus support from the server, since it's not used at all (it was enabled to test a daemon for wacom).

Changed in xorg-server (Ubuntu):
status: Fix Committed → Incomplete
Changed in xorg-server (Ubuntu):
status: Incomplete → Confirmed
Bryce Harrington (bryce) on 2009-08-13
tags: added: jaunty
Adam Nelson (adam-varud) wrote :

This is also a problem with xvfb:

ubuntu$ sudo Xvfb :43 -screen 0 640x480x24
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.84" is not allowed to own the service "org.x.config.display43" due to security policies in the configuration file)
(EE) config/hal: couldn't initialise context: unknown error (null)

I don't think this has anything to do with sugar, except in so much as sugar is hitting the X and dbus errors.

Also, just so nobody asks, there is no Xorg.0.log file on a server with just xvfb. It's not clear to me that xvfb has a method for more logging although I'll run anything people ask me to in order to help debug this.

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
importance: Undecided → Low
assignee: nirmit (nirmit-bothra) → nobody

> Hard to fix since we can't clutter the config file with values until 100.
Timo Aaltonen suggested (in comment #18) to disable the DBus stuff altogether since it's unused. That should be an easy enough fix; is there a reason not to go that route?

Adam Nelson (adam-varud) wrote :

I just uninstalled dbus and all is well:

sudo apt-get remove dbus

Sure, that's really a trivial workaround on a desktop box...

$ sudo apt-get remove dbus
[...]
0 upgraded, 0 newly installed, 361 to remove and 2 not upgraded.
After this operation, 1173MB disk space will be freed.

Are you sure you're using Ubuntu? :D

Adam Nelson (adam-varud) wrote :

I'm using headless Ubuntu and xvfb on an Amazon/Canonical ec2 instance (karmic-updates).

liquidweaver (joshuaweaver) wrote :

Still here in Karmic.

Even when if you edit /etc/dbus-1/system.d/xorg-server.conf to eliminate the dbuss access denied error, you still get a blank black screen in Xnest.

Anish (anishmangal2002) wrote :
Download full text (3.8 KiB)

+1 liquidweaver
Still here in Karmic running on amd64

anish@anish-laptop:~$ sudo sugar-emulator -i 800x600
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.95" is not allowed to own the service "org.x.config.display100" due to security policies in the configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
(EE) XKB: No components provided for device Virtual core keyboard
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.95" is not allowed to own the service "org.x.config.display100" due to security policies in the configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
matchbox: keyboard does not appear to have a <alt> key.
matchbox: ignoring key shortcut <Alt>return=fullscreen

/usr/lib/python2.6/dist-packages/jarabe/desktop/meshbox.py:19: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha

** (sugar-session:4274): WARNING **: Trying to register gtype 'WnckWindowState' as flags when in fact it is of type 'GEnum'

** (sugar-session:4274): WARNING **: Trying ...

Read more...

Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Morgan,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 325706

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 325706 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/325706

Changed in xorg-server (Ubuntu):
status: Triaged → Incomplete
tags: added: needs-retested-on-lucid-by-june

Seems to work here, but I don't think the bug is properly solved. The problem is still the same: D-Bus configuration doesn't allow for more than 3 X displays (:0, :1 and :2), so others will fail.

But maybe I'm missing something, because here Xephyr is on :11 and it works...

Bryce Harrington (bryce) on 2010-05-05
Changed in xorg-server (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
David Farning (dfarning) wrote :

Sorry still learning how to mark something expired.

Changed in sugar:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers