desktop-packages team mailing list archive

[Bryce Harrington <829470@xxxxxxxxxxxxxxxxxx>]

Actually, some light googling shows the 'Xlib: extension "RANDR" missing
on display ":99".' is innocuous and can  be ignored.

I'm able to reproduce the same test failure from the pygtk build
directory without xvfb (i.e. DISPLAY=:0), so this seems not to be a bug
in xvfb but just a failing test that isn't reported well.

@Doko, before I close out the xorg-server task, can you review and see
if you concur, or if I missed something please elaborate.  I spot
checked a few of your other recently reported bugs to see if there are
other instances of xvfb-related failures but didn't see any so am
guessing this is just an outlier.


** Summary changed:

- xvfb failed to start - pygtk version 2.24.0-2 failed to build in oneiric
+ pygtk version 2.24.0-2 failed to build in oneiric

** Changed in: xorg-server (Ubuntu Oneiric)
       Status: Triaged => Incomplete

** Changed in: xorg-server (Ubuntu Oneiric)
   Importance: High => Undecided

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygtk in Ubuntu.
https://bugs.launchpad.net/bugs/829470

Title:
  pygtk version 2.24.0-2 failed to build in oneiric

Status in “pygtk” package in Ubuntu:
  Confirmed
Status in “xorg-server” package in Ubuntu:
  Incomplete
Status in “pygtk” source package in Oneiric:
  Confirmed
Status in “xorg-server” source package in Oneiric:
  Incomplete

Bug description:
  pygtk version 2.24.0-2 failed to build in oneiric
  Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2709047

  Details about the rebuild:
  http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html

  Direct link to the build log: https://launchpad.net/ubuntu/+archive
  /test-rebuild-20110816/+build/2709047/+files/buildlog_ubuntu-
  oneiric-i386.pygtk_2.24.0-2_FAILEDTOBUILD.txt.gz

  This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
  Excerpt 7519 lines into the build log:

  	done
  # finally, install files from DESTDIR in the per-package dirs
  dh_install
  # install rtupdate script to handle Python default runtime change
  install -d debian/python-gtk2-dev/usr/share/python/runtime.d
  install debian/python-gtk2-dev.rtupdate debian/python-gtk2-dev/usr/share/python/runtime.d
  for i in $(find debian/python-*-dbg -name '*.so'); do \
  	  b=$(basename $i .so); \
  	  mv $i $(dirname $i)/${b}_d.so; \
  	done
  dh_testdir
  G_HOME=/ PYTHON=/usr/bin/python2.6 xvfb-run -s "-screen 0 1280x1024x24 -noreset" /usr/bin/make -C build-2.6 check
  xvfb-run: error: Xvfb failed to start
  make: *** [build-2.6/check-stamp] Error 1
  dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary gave error exit status 2
  ******************************************************************************
  Build finished at 20110818-0818
  FAILED [dpkg-buildpackage died]
  Purging chroot-autobuild/build/buildd/pygtk-2.24.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/829470/+subscriptions