After update in intrepid branch Xorg

[PERIER Romain]

This morning, after un dist-upgrade from intrepid branch (mixt system intrepid/hardy) Xorg doesn't want to start with the fallowing message in Xorg.0.log:
(i think that this problem is due to upgrade of defoma).

/var/log/Xorg.0.log :

Could not init font path element /usr/share/fonts/X11/misc, removing from list !
Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list !
Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list !
Could not init font path element /usr/share/fonts/X11/Type1, removing from list !
Could not init font path element /usr/share/fonts/X11/100dpi, removing from list !
Could not init font path element /usr/share/fonts/X11/75dpi, removing from list !

Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list !

Fatal server error :
Could not open default font 'fixed'.

EOF.

i tested to launch fc-cache -fv with sudo i noted that : "/usr/share/fonts/X11/misc : caching, new cache contents, 0 fonts , 0 dirs."

and exactly the same to other bad fonts (75dpi, 100dpi .. etc). the problem is directory /usr/share/fonts/X11/misc is not empty, and the other too and i found fonts.alias...

/usr/share/fonts/truetype are oki !

Extra information :

defoma : 0.11.10-0.2

[easthero (easthero)]

I met the same problem ...
ubuntu8.10

[Gérard Bigot (gerard-bigot)]

me too.

Tried fc-cache -fv, but got the same things than in the bug description. Not-ttf fonts are not seen. ttf fonts are seen but not used. I even have a .fonts/ in my homedir, correctly indexed by fc-cacche, but not used.

G.

[Sense Egbert Hofstede (sense)]

This bug report can be confirmed. Can you please attach /var/log/Xorg.0.log, /var/log/messages and /var/log/syslog? Thanks in advance.

[lemonade (lemonade)]

This error message seems to be connected with update to libxfont1 1.3.2-1. Downgrading to previous version is a temporary fix.

[easthero (easthero)]

here is my xorg.0.log

[PERIER Romain (mrpouet)]

lemonade thanks to information about fixing ... i'll try this.
actually i can't attach my logs, because i'm not at home, i'll attach them later.

[David Futcher (bobbo)]

Have the exact same problem, trying it in Xnest:

bobbo@tiger:~/bin$ Xnest :1 -ac
Could not init font path element /usr/share/fonts/X11/misc, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list!
Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list!
Could not init font path element /usr/share/fonts/X11/Type1, removing from list!
Could not init font path element /usr/share/fonts/X11/100dpi, removing from list!
Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!

Fatal server error:
could not open default font 'fixed'

[Gérard Bigot (gerard-bigot)]

downgrade to libxfont1 version 1.3.1-2. The new one, version 1.3.2-1,
triggers the problem.

G.

On Sun, May 4, 2008 at 4:17 PM, David Futcher <email address hidden> wrote:

> Have the exact same problem, trying it in Xnest:
>
> bobbo@tiger:~/bin$ Xnest :1 -ac
> Could not init font path element /usr/share/fonts/X11/misc, removing from
> list!
> Could not init font path element /usr/share/fonts/X11/cyrillic, removing
> from list!
> Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled,
> removing from list!
> Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled,
> removing from list!
> Could not init font path element /usr/share/fonts/X11/Type1, removing from
> list!
> Could not init font path element /usr/share/fonts/X11/100dpi, removing
> from list!
> Could not init font path element /usr/share/fonts/X11/75dpi, removing from
> list!
> Could not init font path element
> /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!
>
> Fatal server error:
> could not open default font 'fixed'
>
> --
> After update in intrepid branch Xorg
> https://bugs.launchpad.net/bugs/226156
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[David Futcher (bobbo)]

As Chad said in Bug #226514, this can be temporarily fixed by downgrading to the Hardy version:

wget http://ubuntu.blueyonder.co.uk/archive/pool/main/libx/libxfont/libxfont1_1.3.1-2_i386.deb
dpkg -i libxfont1_1.3.1-2_i386.deb

[Vojtěch Trefný (vojtech.trefny)]

Downgrade to libxfont1_1.3.1-2 helped, thanks!

[tao-tao (bouddha)]

For amd64

wget http://fr.archive.ubuntu.com/ubuntu/pool/main/libx/libxfont/libxfont1_1.3.1-2_amd64.deb
dpkg -i libxfont1_1.3.1-2_amd64.deb

[Iain Lane (laney)]

This is a bug in fontconfig, not xorg.

[Iain Lane (laney)]

Erm, I meant libxfont....

[Sergey Fionov (sfionov)]

I was trying to build new libxfont using different LDFLAGS.

Xorg does not start when using libxfont built with default dpkg-buildpackage LDFLAGS="-Wl,-Bsymbolic-functions".
But everything works fine when I use libxfont built with empty LDFLAGS.

[Bryce Harrington (bryce)]

Looks ok to me.

<slangasek> bryce: -Wl,-Bsymbolic-functions is a single option; its purpose is to optimize the start-time symbol resolution at the expense of some "correctness", by causing any references to symbols available within the lib itself to be bound at build time
<bryce> slangasek: ah; is it a new addition? is there risk in turning it off?
<slangasek> bryce: there's no risk at all in turning it off, AFAIK it's entirely a performance thing

[Launchpad Janitor (janitor)]

This bug was fixed in the package libxfont - 1:1.3.2-1ubuntu1

---------------
libxfont (1:1.3.2-1ubuntu1) intrepid; urgency=low

  * debian/rules: Explicetly use empty LDFLAGS, closes LP: #226156.
  * debian/control: Mangle Maintainer field according to spec.

 -- Stefan Potyra <email address hidden> Tue, 13 May 2008 20:00:29 +0200

[Bryce Harrington (bryce)]

Stefan, thanks for the fix. Do you have more background on how the bug manifested itself? Was it an issue with something linking against libxfont? If so, perhaps we need a bug against that package so we can fix it there.

[StefanPotyra (sistpoty)]

Hi Bryce,

Am Mittwoch 14 Mai 2008 18:40:56 schrieb Bryce Harrington:
> Stefan, thanks for the fix. Do you have more background on how the bug
> manifested itself? Was it an issue with something linking against
> libxfont? If so, perhaps we need a bug against that package so we can
> fix it there.

In theory, with -Bsymbolic-functions, you cannot override functions defined in
libxfont1 by programs/libraries linking against libxfont1.

However I'm still trying to bring this theory down to c-code, which will in
fact show different behaviour for different linker options.

As a reminder, I've just filed bug #230460.

I guess it's possible to find out who's the "evildoer" (it might even be done
on purpose) by comparing symbols of libxfont1 with symbols of libs/programs
linking against it, but I'm far from sure there.

Once I know more, I'll post updates to bug #230460.

Cheers,
   Stefan.