[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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 -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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 bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
** 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: 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
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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 received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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 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. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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? -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: 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 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
** 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 because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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) = Canonical Desktop Team (canonical-desktop-team) -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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 xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 632594] Re: xvfb 1.9 and/or metacity not working on the buildds
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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
