ubuntu-x-swat 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 Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/829470

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

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