[nvidia] X segfaults after login in Dispatch+0x1cb due to "ttf-arabeyes" font

Bug #91351 reported by Martin Emrich
8
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: xorg

(Feisty,amd64,nvidia)

After login, I just see the GNOME splash screen "Nautilus...", then the X server crashed and I'm back to textmode. From Xorg.0.log:

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x6d) [0x4827fd]
1: /lib/libc.so.6 [0x2b8514aa2d40]
2: /usr/X11R6/bin/X [0x4fdf57]
3: /usr/X11R6/bin/X(Dispatch+0x1cb) [0x44df4b]
4: /usr/X11R6/bin/X(main+0x45d) [0x43703d]
5: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b8514a8f8e4]
6: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x241) [0x436339]

Fatal server error:
Caught signal 11. Server aborting

Revision history for this message
Martin Emrich (emme) wrote :
Revision history for this message
Martin Emrich (emme) wrote :
Revision history for this message
Martin Emrich (emme) wrote :

I saw this in the changelog.Debian:

    - Re-add 126_debian_always_use_default_font_path.diff. This was dropped
      by Debian but needed by us since we still have legacy fontpaths in
      old configurations, so new paths need to be appended to the list.

So I grabbed the source package, removed this patch, rebuilt and reinstalled xserver-xorg-core. After that, my X works again.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

err, I don't see how that could be related... That patch only makes the server to always check the fontpaths specified with '--with-default-font-path'.

Revision history for this message
Martin Emrich (emme) wrote :

Some possibilities I see:

1. In the logfile, it says "Could not init font path element /usr/X11R6/lib/ X11/fonts/Type1, removing from list!". The spaces between ...lib/ and X11... are also in the debian/rules file, maybe they disturb X.

2. in one of these paths, there is something that does not get along with X and GNOME (Starting X alone without GNOME, it worked all the time). As I now have removed this option, I'll now try to add all the default paths one by one to my xorg.conf and see what happens...

Revision history for this message
Martin Emrich (emme) wrote :

Ok, I did some further tests. I nailed it down to this directory:

/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType

When I enter it into my xorg.conf, X crashes, If I comment it out, my X works normally. So I started removing truetype font packages one by one, and luckily, already the first one worked:

After removing "ttf-arabeyes", my X works even with this directory listed in my config.

So either one of the fonts in ttf-arabeyes causes my X server to crash, or the sum of all fonts including them is too big or too many for X to handle (buffer overflow?). From this point, I actually don't know how to track down the bug further. Some "irregularities" I observed with this font package:

- Three dead symlinks:
ae_AlMohannad.ttf: No such file or directory
ae_AlYermok.ttf: No such file or directory
ae_Mash_bold.ttf: No such file or directory

- While installing, I get some (error?) messages:
martin@garrett:/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType$ sudo apt-get install ttf-arabeyes
...
Entpacke ttf-arabeyes (aus .../ttf-arabeyes_1.1-6_all.deb) ...
Richte ttf-arabeyes ein (1.1-6) ...
No CIDSupplement specified for KochiMincho-Regular-JaH, defaulting to 0.
No CIDSupplement specified for Batang-Regular, defaulting to 0.
No CIDSupplement specified for Gulim-Regular, defaulting to 0.
No CIDSupplement specified for KochiMincho-Regular, defaulting to 0.
No CIDSupplement specified for Dotum-Regular, defaulting to 0.
No CIDSupplement specified for KochiGothic-Regular, defaulting to 0.
No CIDSupplement specified for KochiGothic-Regular-JaH, defaulting to 0.
No CIDSupplement specified for Headline-Regular, defaulting to 0.

Revision history for this message
Guillaume ZITTA (zitta-guillaume) wrote :

Hi, I have the same PB with Beryl

Launching beryl, X crashes with:

Could not init font path element /usr/X11R6/lib/X11/fonts/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/X11R6/lib/X11/fonts/Type1, removing from list!
(II) NVIDIA(0): v4l: memPhysBase=0xe0000000

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x48282d]
1: /lib/libc.so.6 [0x2b5149440d40]
2: /usr/bin/X(Dispatch+0x120) [0x44dea0]
3: /usr/bin/X(main+0x45d) [0x43703d]
4: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b514942d8e4]
5: /usr/bin/X(FontFileCompleteXLFD+0x241) [0x436339]

Fatal server error:
Caught signal 11. Server aborting

Revision history for this message
Bryce Harrington (bryce) wrote : Re: X.Org segfaults after login FontFileCompleteXLFD+0x241 due to "ttf-arabeyes" font

Might be related to bug 71913 or bug 60288, which have similar backtraces

Changed in xorg:
importance: Undecided → High
status: Unconfirmed → Confirmed
Revision history for this message
Jani Averbach (jaa-jaa-iki) wrote :

I have similar backtrace, with few differences:
- I happens if I log out, not when I log in
- If I remove /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType config line from xorg.conf, it doesn't make any difference

temporary fix:
I added TerminateServer=true to my /etc/kde3/kdm/kdmrc file, and that fixed the problem for now.

Also, if you are stuck with blank screen with blinking cursor, kill kdm by hitting
CTRL-ALT-SysRq-K (all the same time), then you will see SysRq: SAK on your virtual terminal,
and after that you can switch to VT1 and restart X.

This is a stock installation of Kubuntu Feisty with normal updates.
01:00.0 VGA compatible controller: S3 Inc. SuperSavage IX/C SDR (rev 05)

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/lib/xorg/modules//libramdac.so(xf86SetCursor+0x10a) [0xafa297ca]
3: /usr/lib/xorg/modules//libramdac.so [0xafa28e35]
4: /usr/bin/X(miPointerUpdate+0x164) [0x811a4e4]
5: /usr/bin/X [0x811a5f9]
6: /usr/bin/X [0x8132a3e]
7: /usr/bin/X [0x8156557]
8: /usr/bin/X(DefineInitialRootWindow+0x12b) [0x8094e3b]
9: /usr/bin/X(main+0x45a) [0x807474a]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7dcbebc]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

Fatal server error:
Caught signal 11. Server aborting

Revision history for this message
LagartoFlojo (lagartoflojo) wrote :

This happens to me in Ubuntu Feisty, but only with the new Intel graphics driver (package xserver-xorg-video-intel).
It does not happen with the old driver (xserver-xorg-video-i810).

I have removed the ttf-arabeyes package and nothing happened.
I have also commented out the pertinent "font path elements" from xorg.conf, but as you can see below, it still tries to initialize them.

00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)

gdm log:
======================
Could not init font path element /usr/X11R6/lib/X11/fonts/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/X11R6/lib/X11/fonts/Type1, removing from list!

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/lib/xorg/modules/drivers//i810_drv.so(intel_xf86CrtcSetMode+0x59) [0xb7b90fc9]
3: /usr/lib/xorg/modules/drivers//i810_drv.so(intel_xf86SetSingleMode+0x11a) [0xb7b913da]
4: /usr/lib/xorg/modules/drivers//i810_drv.so [0xb7b722a0]
5: /usr/lib/xorg/modules//libramdac.so [0xb7a2cb38]
6: /usr/X11R6/bin/X [0x80cdff3]
7: /usr/X11R6/bin/X(xf86SwitchMode+0xce) [0x80c2d0e]
8: /usr/lib/xorg/modules/drivers//i810_drv.so(intel_xf86RandR12SetConfig+0x20c) [0xb7b939bc]
9: /usr/X11R6/bin/X [0x8159466]
10: /usr/X11R6/bin/X [0x81424ce]
11: /usr/X11R6/bin/X(Dispatch+0x19f) [0x808c61f]
12: /usr/X11R6/bin/X(main+0x495) [0x8074785]
13: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d44ebc]
14: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

Fatal server error:
Caught signal 11. Server aborting
========================

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Can any of you reproduce this with 7.10 or Hardy?

Changed in xorg:
status: Confirmed → Incomplete
Revision history for this message
Martin Emrich (emme) wrote :

Hi!

I am sorry, but I now have an AMD onboard graphics card, so I cannot test it anymore.

Ciao

Martin

Revision history for this message
LagartoFlojo (lagartoflojo) wrote :

The problem as I reported it has been solved in Gutsy (same hardware).

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Ok, I'll close the bug as fixed, thanks!

Changed in xorg:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.