ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #87782
[Bug 632594] [NEW] xvfb 1.9 and/or metacity not working on the buildds
Public bug reported:
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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: "(null)" found in configuration database is not a valid value for mouse button modifier
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: Could not parse font description "(null)" from GConf key /apps/metacity/general/titlebar_font
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: 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 /apps/metacity/general/num_workspaces is out of range 1 to 36
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!
** Affects: metacity (Ubuntu)
Importance: High
Status: Confirmed
** Affects: xorg-server (Ubuntu)
Importance: High
Status: Confirmed
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: metacity (Ubuntu)
Importance: Undecided => High
** Changed in: metacity (Ubuntu)
Status: New => Confirmed
** Changed in: metacity (Ubuntu)
Milestone: None => ubuntu-10.10
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => High
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
** Changed in: xorg-server (Ubuntu)
Milestone: None => ubuntu-10.10
--
xvfb 1.9 and/or metacity not working on the buildds
https://bugs.launchpad.net/bugs/632594
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Follow ups
-
[Bug 632594] Re: metacity causing xvfb to not work on the buildds
From: Launchpad Bug Tracker, 2011-04-08
-
[Bug 632594] Re: metacity causing xvfb to not work on the buildds
From: Martin Pitt, 2011-02-04
-
[Bug 632594] Re: metacity causing xvfb to not work on the buildds
From: Launchpad Bug Tracker, 2010-11-30
-
[Bug 632594] Re: metacity causing xvfb to not work on the buildds
From: Launchpad Bug Tracker, 2010-11-30
-
[Bug 632594] Re: metacity causing xvfb to not work on the buildds
From: Launchpad Bug Tracker, 2010-11-30
-
[Bug 632594] Re: metacity causing xvfb to not work on the buildds
From: Matthias Klose, 2010-11-21
-
[Bug 632594] Re: metacity causing xvfs to not work on the buildds
From: Matthias Klose, 2010-11-21
-
[Bug 632594] Re: metacity causing xvfs to not work on the buildds
From: Guillaume Mazoyer, 2010-11-19
-
[Bug 632594] Re: metacity causing xvfs to not work on the buildds
From: Martin Pitt, 2010-11-19
-
[Bug 632594] Re: metacity causing xvfs to not work on the buildds
From: Martin Pitt, 2010-11-19
-
[Bug 632594] Re: metacity causing xvfs to not work on the buildds
From: Matthias Klose, 2010-10-28
-
[Bug 632594] Re: metacity not working on the buildds
From: Kees Cook, 2010-10-28
-
[Bug 632594] Re: metacity not working on the buildds
From: Bryce Harrington, 2010-10-28
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Matthias Klose, 2010-10-28
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Andrew Cowie, 2010-10-28
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Bryce Harrington, 2010-10-28
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Guillaume Mazoyer, 2010-10-27
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Bryce Harrington, 2010-10-27
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Bryce Harrington, 2010-10-27
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Bryce Harrington, 2010-10-27
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Bryce Harrington, 2010-10-27
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Bryce Harrington, 2010-10-27
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Guillaume Mazoyer, 2010-10-24
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Kate Stewart, 2010-10-20
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Didier Roche, 2010-09-24
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Matthias Klose, 2010-09-08
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Matthias Klose, 2010-09-08
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Matthias Klose, 2010-09-08
-
[Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
From: Matthias Klose, 2010-09-08
-
[Bug 632594] [NEW] xvfb 1.9 and/or metacity not working on the buildds
From: Matthias Klose, 2010-09-07
References