desktop-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

Running by hand, I see:

$ fakeroot Xvfb :99 -noreset -nolisten tcp(EE) GLX: could not load software renderer
[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!
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:            Cannot open "/var/lib/xkb/file8s3uEn" to write keyboard description
>                   Exiting
(EE) Error compiling keymap (-)
(EE) XKB: Couldn't compile keymap
(EE) XKB: Failed to load keymap. Loading default keymap instead.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:            Cannot open "/var/lib/xkb/file64o1de" to write keyboard description
>                   Exiting
(EE) Error compiling keymap (-)
(EE) XKB: Couldn't compile keymap
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.

Fatal server error:
Failed to activate core devices.
$

So if xvfb thinks it's root (which is the purpose of fakeroot), it fails
to start if it can't write to /var/lib/xkb.

-- 
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:
  Confirmed
Status in “pygtk” source package in Oneiric:
  Confirmed
Status in “xorg-server” source package in Oneiric:
  Confirmed

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