[intrepid]: broken

Bug #229079 reported by StefanPotyra
This bug report is a duplicate of:  Bug #226156: After update in intrepid branch Xorg . Edit Remove
8
Affects Status Importance Assigned to Milestone
libxfont (Ubuntu)
Confirmed
High
Unassigned
Nominated for Intrepid by Sebastian Rode

Bug Description

Hi,

currently, libxfonts1 is severly broken, resulting in X not starting. Fortunately, Fujitsu pointed me out to this issue, and wrote that downgrading will work (which it does).

working version: 1:1.3.1-2
not working version: 1:1.3.2-1

kdm.log snippet:
Current Operating System: Linux suut 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64
Build Date: 15 April 2008 05:41:18PM

        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat May 10 21:34:17 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "i2c" already built-in
(II) Module "ddc" already built-in
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) Failed to load module "xrandr" (module does not exist, 0)
(EE) Failed to load module "composite" (module does not exist, 0)
(II) Module "ramdac" already built-in
expected keysym, got XF86KbdLightOnOff: line 70 of pc
expected keysym, got XF86KbdBrightnessDown: line 71 of pc
expected keysym, got XF86KbdBrightnessUp: line 72 of pc
expected keysym, got XF86KbdLightOnOff: line 70 of pc
expected keysym, got XF86KbdBrightnessDown: line 71 of pc
expected keysym, got XF86KbdBrightnessUp: line 72 of pc
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Could not init font path element /usr/share/X11/fonts/misc, removing from list!
Could not init font path element /usr/share/X11/fonts/100dpi/:unscaled, removing from list!
Could not init font path element /usr/share/X11/fonts/75dpi/:unscaled, removing from list!
Could not init font path element /usr/share/X11/fonts/Type1, removing from list!
Could not init font path element /usr/share/X11/fonts/100dpi, removing from list!
Could not init font path element /usr/share/X11/fonts/75dpi, removing from list!
Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!
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'

anything else you need?

Cheers,
     Stefan.

Revision history for this message
StefanPotyra (sistpoty) wrote :

confirmed/high.

Changed in libxfont:
importance: Undecided → High
status: New → Confirmed
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.