| 1 |
Donnie Berkholz <dberkholz@g.o> posted |
| 2 |
20080906072011.GA16219@comet, excerpted below, on Sat, 06 Sep 2008 |
| 3 |
00:20:11 -0700: |
| 4 |
|
| 5 |
> I've just added xorg-server 1.5 and mesa 7.1 to the tree as ~arch. They |
| 6 |
> will be part of the X.Org 7.4 release to come out shortly, along with a |
| 7 |
> number of other libraries and such that I've recently bumped. |
| 8 |
> |
| 9 |
> Please test them and report any bugs you come across, along with `emerge |
| 10 |
> --info`, /var/log/Xorg.0.log and /etc/X11/xorg.conf. |
| 11 |
|
| 12 |
I merged and thought everything was fine... right up until I tried to run |
| 13 |
pan... but from my research it's going to hit other GTK/GNOME apps too -- |
| 14 |
but KDE (3.5) doesn't seem to be affected. |
| 15 |
|
| 16 |
Turns out I was hit by the dix/xfs/fixed font bug, which Fedora folks |
| 17 |
seem to have already hit, so a Google gave me enough to go on to fix it. |
| 18 |
|
| 19 |
You'll almost certainly want to apply the patch (from upstream) that can |
| 20 |
be found on fedora's bugzi, along with the details of the problem, here: |
| 21 |
|
| 22 |
https://bugzilla.redhat.com/show_bug.cgi?id=430416 |
| 23 |
|
| 24 |
Alternatively, and you may wish to do this anyway, elog a warning |
| 25 |
suggesting people disable (remove from their runlevels, and unmerge after |
| 26 |
testing) xfs (X font server, not the filesystem) unless they really know |
| 27 |
what they are doing with it. The problem manifests as an X <> xfs |
| 28 |
miscommunication when xfs is started before X, tho it works fine if |
| 29 |
started after X, and the root (according to the fedora bug) is a bad |
| 30 |
update to dix. Thus, disabling xfs "cures" (really, avoids) the problem, |
| 31 |
by not starting xfs at startup so it's not running when X starts, thereby |
| 32 |
allowing X to use its internal font system. That's what I'm doing now, |
| 33 |
as I was only running xfs since that's the way I had it setup long ago. |
| 34 |
|
| 35 |
Either way, there's likely to be a lot of people with almost non- |
| 36 |
functional GNOME, pretty much anyone running xfs, according to that bug, |
| 37 |
if something isn't done to either patch the issue or warn them to turn |
| 38 |
off xfs. Luckily I'm a KDE user here and it wasn't much affected. I |
| 39 |
only noticed it when pan wouldn't load, and started spitting BadName |
| 40 |
(named color or font does not exist) errors when run from a terminal |
| 41 |
window. Of course it's pan I use on the lists (thru gmane), so that |
| 42 |
pretty much killed my ability to ask about it here, tho I could have used |
| 43 |
the web interface or mailed directly if I had to. Fortunately it didn't |
| 44 |
get that far, however, as googling the error turned up the Fedora link |
| 45 |
above, and following its advice to turn off xfs effectively avoided |
| 46 |
further problems here. Pan's working fine again, thus this post. =:^) |
| 47 |
|
| 48 |
-- |
| 49 |
Duncan - List replies preferred. No HTML msgs. |
| 50 |
"Every nonfree program has a lord, a master -- |
| 51 |
and if you use the program, he is your master." Richard Stallman |
Archives