Ubuntu
xorg-server package

metacity causing xvfb to not work on the buildds

Bug #632594 reported by Matthias Klose
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Invalid
High
Canonical Desktop Team
Maverick
Invalid
High
Unassigned
Natty
Invalid
High
Canonical Desktop Team
openjdk-6 (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Fix Released
Undecided
Unassigned
Natty
Won't Fix
Undecided
Unassigned
openjdk-6b18 (Ubuntu)
Invalid
Undecided
Unassigned
Maverick
Fix Released
Undecided
Unassigned
Natty
Invalid
Undecided
Unassigned
xorg-server (Ubuntu)
Invalid
High
Canonical Desktop Team
Maverick
Invalid
High
Canonical Desktop Team
Natty
Invalid
High
Canonical Desktop Team

Bug Description

see the openjdk build logs, e.g.

  https://launchpad.net/ubuntu/+source/openjdk-6/6b20-1.9-0ubuntu1

is this a metacity configuration error, or an xvfb error?

the last working build was on Jul 30:
https://launchpad.net/ubuntu/maverick/+source/openjdk-6/6b20~pre2-0ubuntu2

mkdir -p bin
( \
   echo '#!/bin/sh'; \
   echo 'metacity &'; \
   echo 'pid=$!'; \
   echo 'sleep 3'; \
   echo '"$@"'; \
   echo 'kill -9 $pid'; \
 ) > bin/my-jtreg-run
chmod 755 bin/my-jtreg-run
echo 'xvfb-run -a -e xvfb-run.log -s "-extension GLX" my-jtreg-run "$@"' > bin/my-xvfb-run
if ! /bin/sh bin/my-xvfb-run true ; then \
   echo "error running $(cat bin/my-xvfb-run)"; \
   cat xvfb-run.log; \
   echo 'xvfb-run -a -e xvfb-run.log -s "$@"' > bin/my-xvfb-run; \
   if ! /bin/sh bin/my-xvfb-run true ; then \
     echo "error running $(cat bin/my-xvfb-run)"; \
     cat xvfb-run.log; \
     rm -f bin/my-xvfb-run; \
   fi; \
 fi
Window manager warning: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory)
Window manager warning: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory)
...
Window manager warning: 0 stored in GConf key /desktop/gnome/peripherals/mouse/cursor_size is out of range 1 to 128
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory)
**
metacity:ERROR:core/prefs.c:2495:meta_prefs_get_workspace_name: assertion failed: (workspace_names[i] != NULL)
kill: 6: No such process

error running xvfb-run -a -e xvfb-run.log -s "-extension GLX" my-jtreg-run "$@"
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
[dix] Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!
5 XSELINUXs still allocated at reset
SCREEN: 0 objects of 64 bytes = 0 total bytes 0 private allocs
DEVICE: 4 objects of 16 bytes = 64 total bytes 0 private allocs
CLIENT: 0 objects of 92 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 16 bytes = 0 total bytes 0 private allocs
PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs
GC: 0 objects of 44 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 5 objects, 72 bytes, 0 allocs
4 DEVICEs still allocated at reset
DEVICE: 4 objects of 16 bytes = 64 total bytes 0 private allocs
CLIENT: 0 objects of 92 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 16 bytes = 0 total bytes 0 private allocs
PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs
GC: 0 objects of 44 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 5 objects, 72 bytes, 0 allocs
1 PIXMAPs still allocated at reset
PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs
GC: 0 objects of 44 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 8 bytes, 0 allocs
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
[dix] Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!
xvfb-run: usage error: need a command to run
Usage: xvfb-run [OPTION ...] COMMAND
Run COMMAND (usually an X client) in a virtual X server environment.
Options:
-a --auto-servernum try to get a free server number, starting at
                                    --server-num
-e FILE --error-file=FILE file used to store xauth errors and Xvfb
                                    output (default: xvfb-run.log)
-f FILE --auth-file=FILE file used to store auth cookie
                                    (default: ./.Xauthority)
-h --help display this usage message and exit
-n NUM --server-num=NUM server number to use (default: 99)
-l --listen-tcp enable TCP port listening in the X server
-p PROTO --xauth-protocol=PROTO X authority protocol name to use
                                    (default: xauth command's default)
-s ARGS --server-args=ARGS arguments (other than server number and
                                    "-nolisten tcp") to pass to the Xvfb server
                                    (default: "true")
-w DELAY --wait=DELAY delay in seconds to wait for Xvfb to start
                                    before running COMMAND (default: 3)
error running xvfb-run -a -e xvfb-run.log -s "$@"
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
[dix] Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!
5 XSELINUXs still allocated at reset
SCREEN: 0 objects of 64 bytes = 0 total bytes 0 private allocs
DEVICE: 4 objects of 16 bytes = 64 total bytes 0 private allocs
CLIENT: 0 objects of 92 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 16 bytes = 0 total bytes 0 private allocs
PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs
GC: 0 objects of 44 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 5 objects, 72 bytes, 0 allocs
4 DEVICEs still allocated at reset
DEVICE: 4 objects of 16 bytes = 64 total bytes 0 private allocs
CLIENT: 0 objects of 92 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 16 bytes = 0 total bytes 0 private allocs
PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs
GC: 0 objects of 44 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 5 objects, 72 bytes, 0 allocs
1 PIXMAPs still allocated at reset
PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs
GC: 0 objects of 44 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 8 bytes, 0 allocs
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/Type1, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
[dix] Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!

See original description
Matthias Klose (doko)
Changed in metacity (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-10.10
status: New → Confirmed
Changed in xorg-server (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-10.10
status: New → Confirmed
Revision history for this message
Matthias Klose (doko) wrote :

works in unstable with metacity 1:2.30.1-2 and xvfb 2:1.7.7-5

Revision history for this message
Matthias Klose (doko) wrote :

builds on lucid run the tests sucessfully, see https://launchpad.net/~openjdk/+archive/ppa/+packages

Revision history for this message
Matthias Klose (doko) wrote :

davis still has xvfb 2:1.8.1.902-0ubuntu2 installed. upgraded the to the recent metacity. Now it looks like a regression in xvfb.

Revision history for this message
Matthias Klose (doko) wrote :

ohh, and xvfb 2:1.8.1.902-0ubuntu2 does work (at least on powerpc)

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Subscribing the team for now. Will ask for RAOF to look at the xorg side, I'll have a look at the metacity one.

Changed in xorg-server (Ubuntu):
assignee: nobody → Ubuntu Desktop (ubuntu-desktop)
assignee: Ubuntu Desktop (ubuntu-desktop) → Canonical Desktop Team (canonical-desktop-team)
Kate Stewart (kate.stewart)
Changed in xorg-server (Ubuntu):
milestone: ubuntu-10.10 → maverick-updates
Changed in metacity (Ubuntu):
milestone: ubuntu-10.10 → maverick-updates
Revision history for this message
Guillaume Mazoyer (respawneral) wrote :

I can confirm this bug. I got some build failed on a PPA.
Here is one of those https://launchpad.net/~gnome-split-team/+archive/ppa/+build/1982159
The package uses xvfb and Metacity when taking some screenshots to generate the *doc package.

Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

In the error handling branch, the following call is erroneous:

   echo 'xvfb-run -a -e xvfb-run.log -s "$@"' > bin/my-xvfb-run; \

^ this command is missing a command to run. See xvfb-run --help

Revision history for this message
Bryce Harrington (bryce) wrote :

As to the question of how it entered the error path, I can't reproduce the issue on maverick (pasting in the code and running it on a laptop seems to work fine for me). However, from the error messages in the description:

Window manager warning: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory)

...this seems to be suggesting your dbus service is missing. Is that a possibility?

Revision history for this message
Bryce Harrington (bryce) wrote :

The build log in comment #6 doesn't really give enough detail to be sure what the error is, other than just that metacity couldn't be started up:

JAVA Harness
EXEC Xvfb
EXEC metacity
KILL Xvfb
KILL metacity
Exception in thread "main" java.lang.RuntimeException:
metacity didn't start
 at Harness.checkAlive(Harness.java:322)
 at Harness.main(Harness.java:139)
make[1]: *** [doc] Error 1
make[1]: Leaving directory `/build/buildd/java-gnome-4.0.16'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

So, would be interesting to see a more detailed log, but seems quite possible it could be the same bug.

Revision history for this message
Bryce Harrington (bryce) wrote :

Looking at the log from comment #6 it looks like dbus, libdbus, dbus-x11 et al get installed. I can't tell that the dbus service was actually started up though.

Revision history for this message
Guillaume Mazoyer (respawneral) wrote :

Until Maverick, the build always worked. With Maverick, the build works in a local pbuilder but fails due to xvfb and metacity (apparently) on Launchpad. That is how I concluded that it was probably related to this bug.
 but I'm not sure at 100%.

Revision history for this message
Bryce Harrington (bryce) wrote :

I spoke with kees about this this evening. X doesn't depend directly on dbus; it sounds like it is metacity's dbus dependency which is faulting here. Metacity exits with an error, so xvfb propagates that error up.

Revision history for this message
Andrew Cowie (afcowie) wrote :

If it's a case of a DBus dependency (and if not, we're swerving off topic here) then the question is how to run a "private" DBus instance for the build in question.

I ran into this ~2 years ago in that I had to run a a gnome-settings-daemon privately under the Xvfb for metacity's themes to work, but that *broke* when it all moved to DBus because gnome-settings-daemon would quit with an error saying there already was already such a daemon one on the bus ... ie, the real Desktop's one!

So how to start a new DBus channel that offers test / build isolation but which everything running under that (X server?) would find (rather than the user's real one, I don't know.

AfC

Revision history for this message
Matthias Klose (doko) wrote :

the failure mentioned in comment #7 is a followup error (trying to run xvfb without xserver args (-s ...)). the primary failure is still to get metacity starting / working the chroot.

Bryce Harrington (bryce)
summary: - xvfb 1.9 and/or metacity not working on the buildds
+ metacity not working on the buildds
Changed in xorg-server (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Kees Cook (kees) wrote : Re: metacity not working on the buildds

While this may be a metacity bug, i'd still like to see xvfb tested during the build of xorg-server in an attempt to detect future failures.

Changed in xorg-server (Ubuntu):
status: Invalid → Confirmed
summary: - metacity not working on the buildds
+ metacity causing xvfs to not work on the buildds
Changed in metacity (Ubuntu Maverick):
milestone: none → maverick-updates
Changed in xorg-server (Ubuntu Maverick):
milestone: none → maverick-updates
Changed in xorg-server (Ubuntu Natty):
milestone: maverick-updates → natty-alpha-2
Changed in metacity (Ubuntu Natty):
milestone: maverick-updates → natty-alpha-2
Changed in metacity (Ubuntu Maverick):
status: New → Confirmed
importance: Undecided → High
Changed in xorg-server (Ubuntu Maverick):
status: New → Confirmed
importance: Undecided → High
Changed in metacity (Ubuntu Natty):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Changed in metacity (Ubuntu Maverick):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Changed in xorg-server (Ubuntu Maverick):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
Matthias Klose (doko) wrote : Re: metacity causing xvfs to not work on the buildds

according to pitti, metacity has to be launched using dbus-launch, apparently the dependency on gconf requires this in maverick.

Revision history for this message
Martin Pitt (pitti) wrote :

Right, running metacity through "dbus-launch" should work, and I believe Matthias confirmed that on UDS. Can this be closed?

Changed in xorg-server (Ubuntu Maverick):
status: Confirmed → Invalid
Changed in xorg-server (Ubuntu Natty):
status: Confirmed → Invalid
Changed in metacity (Ubuntu Natty):
status: Confirmed → Incomplete
Changed in metacity (Ubuntu Maverick):
status: Confirmed → Incomplete
Changed in xorg-server (Ubuntu Maverick):
milestone: maverick-updates → none
Changed in xorg-server (Ubuntu Natty):
milestone: natty-alpha-2 → none
Revision history for this message
Martin Pitt (pitti) wrote :

Even if there's something we can do for natty to make this easier, it's not important enough for an SRU.

Changed in metacity (Ubuntu Maverick):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
milestone: maverick-updates → none
status: Incomplete → Won't Fix
Revision history for this message
Guillaume Mazoyer (respawneral) wrote :

Lanching Metacity using dbus-launch actually works. Thank you for the tip.

Matthias Klose (doko)
Changed in metacity (Ubuntu Natty):
status: Incomplete → Invalid
Changed in metacity (Ubuntu Maverick):
status: Won't Fix → Invalid
summary: - metacity causing xvfs to not work on the buildds
+ metacity causing xvfb to not work on the buildds
Matthias Klose (doko)
Changed in openjdk-6b18 (Ubuntu Natty):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package openjdk-6b18 - 6b18-1.8.3-0ubuntu1

---------------
openjdk-6b18 (6b18-1.8.3-0ubuntu1) maverick-security; urgency=low

  * IcedTea6 1.8.3 release.
    - CVE-2010-3860: Fix IcedTea System property information leak via
      public static.
  * Start metacity using dbus-launch, when running the testsuite. LP: #632594.
 -- Matthias Klose <email address hidden> Sun, 21 Nov 2010 17:12:01 +0100

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package openjdk-6 - 6b20-1.9.2-0ubuntu1

---------------
openjdk-6 (6b20-1.9.2-0ubuntu1) maverick-security; urgency=low

  * IcedTea6 1.9.2 release.
    - CVE-2010-3860: Fix IcedTea System property information leak via
      public static.
  * Build using Hotspot hs19.
  * Start metacity using dbus-launch, when running the testsuite. LP: #632594.
 -- Matthias Klose <email address hidden> Sun, 21 Nov 2010 18:30:39 +0100

Changed in openjdk-6 (Ubuntu Maverick):
status: New → Fix Released
Changed in openjdk-6b18 (Ubuntu Maverick):
status: New → Fix Released
Martin Pitt (pitti)
Changed in metacity (Ubuntu Natty):
milestone: natty-alpha-2 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package openjdk-6 - 6b27-1.12.3-0ubuntu1~08.04.1

---------------
openjdk-6 (6b27-1.12.3-0ubuntu1~08.04.1) hardy-security; urgency=low

  * Build for 08.04.
 -- Matthias Klose <email address hidden> Tue, 19 Feb 2013 23:57:58 +0100

Changed in openjdk-6 (Ubuntu):
status: New → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

natty has seen the end of its life and is no longer receiving any updates. Marking the natty task for this ticket as "Won't Fix".

Changed in openjdk-6 (Ubuntu Natty):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.