desktop-packages team mailing list archive

[Bryce Harrington <829470@xxxxxxxxxxxxxxxxxx>]

No, there seems to be more to it than that.

root@clanfield:~# ls /var/lib/xkb/
server-02D8252E59564A234380F1E5417646A9DB3B7452.xkm  server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
root@clanfield:~# rm /var/lib/xkb/*
root@clanfield:~# fakeroot Xvfb :99 -noreset -nolisten tcp
[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/100dpi, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
^C/usr/bin/fakeroot: line 1: kill: (4379) - No such process
root@clanfield:~# ls /var/lib/xkb/
server-02D8252E59564A234380F1E5417646A9DB3B7452.xkm

And in a freshly upgraded chroot:

(chroot)root@humber:~# rm /var/lib/xkb/server-*.xkm 
(chroot)root@humber:~# fakeroot Xvfb :99 -noreset -nolisten tcp
[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/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!
^C(chroot)root@humber:~# ls /var/lib/xkb/
server-02D8252E59564A234380F1E5417646A9DB3B7452.xkm

I think the empty /var/lib/xkb/ may be a symptom rather than a root
cause.  Guessing that in the buildd's there's no keyboard so no compiled
xkb keymap is going to get generated.

Martin, can you elaborate on how you're reproducing it?  Are you doing
it in a local chroot or on a buildd?

-- 
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:
  Xvfb fails with empty /var/lib/xkb, causing build failures

Status in “pygtk” package in Ubuntu:
  Invalid
Status in “xorg-server” package in Ubuntu:
  Triaged
Status in “pygtk” source package in Oneiric:
  Invalid
Status in “xorg-server” source package in Oneiric:
  Triaged

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