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,
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.
--
xvfb 1.9 and/or metacity not working on the buildds
https://bugs.launchpad.net/bugs/632594
You received this
** Description changed:
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:
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
--
xvfb 1.9 and/or metacity not working on the buildds
https://bugs.launchpad.net/bugs/632594
You
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:
JAVAHarness
EXECXvfb
EXECmetacity
KILLXvfb
KILLmetacity
Exception in thread main java.lang.RuntimeException:
metacity didn't start
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
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.
--
xvfb 1.9 and/or metacity not working on the buildds
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.
--
xvfb 1.9 and/or metacity not working on the
** Changed in: xorg-server (Ubuntu)
Milestone: ubuntu-10.10 = maverick-updates
** Changed in: metacity (Ubuntu)
Milestone: ubuntu-10.10 = maverick-updates
--
xvfb 1.9 and/or metacity not working on the buildds
https://bugs.launchpad.net/bugs/632594
You received this bug notification
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: (unassigned) = Ubuntu Desktop (ubuntu-desktop)
** Changed in: xorg-server (Ubuntu)
Assignee: Ubuntu Desktop (ubuntu-desktop) =
works in unstable with metacity 1:2.30.1-2 and xvfb 2:1.7.7-5
--
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.
builds on lucid run the tests sucessfully, see
https://launchpad.net/~openjdk/+archive/ppa/+packages
--
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
ohh, and xvfb 2:1.8.1.902-0ubuntu2 does work (at least on powerpc)
--
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.
13 matches
Mail list logo
