Bug#661073: xorg: crashes running: emacs, gv, various web pages
On Thu, Mar 01, 2012 at 11:41:59AM -0500, Jeffrey Sheinberg wrote:
> Hi Julien,
>
> 1. Yes, this is intentional.
>
> 2. Because this was the easiest for me way to disable the framebuffer.
>
> I don't like the framebuffer because I find it to be visually disturbing
> when it scrolls. I am working on finding a better way to disable the
> framebuffer (modinfo for ttm,drm,drm_kms_helper,fbcon).
>
> As far as KMS vs. UMS is concerned, they are both about the same for me,
> ie, buggy. It goes like this,
...
Hi,
In order to get my system to suspend and awake properly, I use this
command,
# pm-suspend --quirk-s3-bios --quirk-s3-mode --store-quirks-as-lkw
I have a feeling that the KMS and UMS corruption that I experience with
xorg is caused by the KMS and UMS code not being aware of the need to
use the above quirks with my system.
Now for the good news - I have found how to "stop the x-server from
crashing", which is the original topic of this bug report.
Cyril was on the right track when he suggested that I remove my custom
font config from the $xconfig file.
Eventually, I got to thinking "why does running a simple command such
as "xlsfonts" immediately cause the x-server to crash? So, I then purged
each of these packages - "xfs" and "xfstt". Now, poof, this bug is gone!
IIRC, there is no configuration for "xfstt", however, there is a configuration
file for "xfs", namely, "/etc/X11/fs/config". Here is a diff of my
configuration for "/etc/X11/fs/config" against its dist conffile,
just in case someone is interested trying to reproduce this bug,
--- etc.X11.fs.RCS.config 2012-03-12 12:52:29-04 1.1
+++ etc.X11.fs.RCS.config 2012-03-12 12:54:30-04 1.2
@@ -12,9 +12,20 @@ clone-self = on
use-syslog = on
# turn off TCP port listening (Unix domain connections are still permitted)
no-listen = tcp
-# paths to search for fonts
-catalogue = /usr/share/fonts/X11/misc/,/usr/share/fonts/X11/cyrillic/,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1/,/usr/share/fonts/X11/100dpi/,/usr/share/fonts/X11/75dpi/
+
+# Paths to search for fonts - keep in sync with "${xconfig}" file.
+## Put each of these just prior to *its corresponding* X11/fonts entry,
+## /home/jsroot/fonts/xfree86-3.3.x/misc/,
+catalogue =
+ /usr/share/fonts/X11/misc/,
+ /usr/share/fonts/X11/75dpi/:unscaled,
+ /usr/share/fonts/X11/100dpi/:unscaled,
+ /usr/share/fonts/X11/Type1/,
+ /usr/share/fonts/X11/75dpi/,
+ /usr/share/fonts/X11/100dpi/
+# Note - Defoma font paths are appended in "${xcli}" via "xset".
+
# in decipoints
default-point-size = 120
# x1,y1,x2,y2,...
-default-resolutions = 100,100,75,75
+default-resolutions = 75,75,100,100
Also, I no longer append the defoma font paths in my .xclients file, instead,
I just have them hard coded into my "$xconfig" file.
Here is the current font path, via "xset q", now that this bug no longer
happening on my system,
/usr/share/fonts/X11/misc/,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1/,/usr/share/fonts/X11/100dpi/,/usr/share/fonts/X11/75dpi/,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/,built-ins
Of course, placing the blame on "xfs" or "xfstt" is only speculation on
my part. I am just so happy that this bug has disappeared from my system,
after having removed "xfs" and "xfstt".
Thanks,
--
Jeffrey Sheinberg
Reply to: