Description of problem: $cat Xorg.0.log [...] 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/100dpi:unscaled, removing from list! Could not init font path element /usr/share/X11/fonts/misc: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/fonts/default/Type1, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/hanyang, removing from list! Fatal server error: could not open default font 'fixed' Version-Release number of selected component (if applicable): 1.2.3-3.fc7 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: No problem in libXfont-1.2.2-1.fc6
Created attachment 141763 [details] /var/log/Xorg.0.log in libXfont-1.2.3-3.fc7
Created attachment 141775 [details] Xorg log output.... Get similar failure to start up graphical login.... Here is output from running 'startx': [root@localhost ~]# cat err xauth: creating new authority file /root/.serverauth.3261 X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: Fedora Core 5 Red Hat, Inc. Current Operating System: Linux localhost.localdomain 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 Build Date: 10 November 2006 Build ID: xorg-x11-server 1.1.1-51.fc7 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: Tue Nov 21 07:00:12 2006 (==) Using config file: "/etc/X11/xorg.conf" (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found (1600x1200,Monitor0) mode clock 162MHz exceeds DDC maximum 140MHz Could not init font path element unix/:7100, removing from list! Could not init font path element built-ins, removing from list! Fatal server error: could not open default font 'fixed' XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. [root@localhost ~]# Reverting 'libfont*' and 'libXfont*' packages restores function.
I can confirm that also...
Same problem here. xfs crashes with this version of libXfont. Running 'xfs -nodaemon' yields: "xfs fatal error: element #0 (starting at 0) of font path is bad or has a bad font."
Down for the count also. Adding to CC:
Created attachment 141852 [details] Xorg log with usually working dual head
Rolling back to FC6 versions of libXfont avd associated packages is all that was needed in order to get development back up and running in GUI. No other packages are reverted. Output below from pup - Update details. libXfont-devel - 1.2.3-3.fc7.i386 updates libXfont-devel - 1.2.2-1.fc6.i386 libXfont - 1.2.3-3.fc7.i386 updates libXfont - 1.2.2-1.fc6.i386 Like Baretta, just don't do it.
after rolling back to the FC6 versions of libXfont - X11 is running again. But I'm now only able to run failsafe sessions! There must be also something going wrong with KDE because the KDM login window reappears immediately after entering name and password. PS: Is there a lynx optimated interface of bugzilla available ? It's very hard to look for bug reports in bugzilla when X11 doesn't run.
*** Bug 217032 has been marked as a duplicate of this bug. ***
Reproducive on "Intel Corporation 82852/855GM Integrated Graphics Device". However, I tried installing mockbuild libXfont-1.2.3-3.fc7.i386 with libXfont-1.2.3-namespace-pollution.patch _removed_ and for now there seems no problem.
Seems to be fixed in version 1.2.3-4.fc7!
(In reply to comment #11) > Seems to be fixed in version 1.2.3-4.fc7! ...because the namespace patches was backed out, which I guess means 1.2.4-4 is the same thing as 1.2.3-1, right? I'd like to notice that this hasn't got anything with xfs to do. I don't use xfs (I simply put the paths directly in xorg.conf).
Fixed now.