X Strike Force XFree86 SVN commit: r1716 - in trunk/debian: . local
Author: branden
Date: 2004-08-09 13:43:34 -0500 (Mon, 09 Aug 2004)
New Revision: 1716
Modified:
trunk/debian/CHANGESETS
trunk/debian/local/FAQ.xhtml
Log:
(cosmetic) Make more stylistic and typographical fixes.
Modified: trunk/debian/CHANGESETS
===================================================================
--- trunk/debian/CHANGESETS 2004-08-09 18:21:34 UTC (rev 1715)
+++ trunk/debian/CHANGESETS 2004-08-09 18:43:34 UTC (rev 1716)
@@ -14,7 +14,7 @@
Miscellaneous cosmetic fixes.
1607, 1608, 1624, 1626, 1627, 1636, 1651, 1654, 1663, 1664, 1675, 1685,
- 1690, 1713, 1715
+ 1690, 1713, 1715, 1716
Grab latest version of XTerm (#191) from Thomas Dickey's website.
1609
Modified: trunk/debian/local/FAQ.xhtml
===================================================================
--- trunk/debian/local/FAQ.xhtml 2004-08-09 18:21:34 UTC (rev 1715)
+++ trunk/debian/local/FAQ.xhtml 2004-08-09 18:43:34 UTC (rev 1716)
@@ -1190,11 +1190,12 @@
functioning for some people who had not paid close attention to their XKB
configuration in the past. Users of 102- or 105-key PC keyboards (as well as
miniature and laptop keyboards compatible with these models) should ensure that
-their keyboard is configured accordingly in the XF86Config-4 file, using the
-<code style="other">pc102</code> or <code style="other">pc105</code> <code
+their keyboard is configured accordingly in the <code
+style="filespec">XF86Config-4</code> file, using the <code
+style="other">pc102</code> or <code style="other">pc105</code> <code
style="other">XkbModel</code> instead of <code style="other">pc101</code> or
<code style="other">pc104</code>, respectively. U.S.-style PC keyboards do not
-have a "< >" key, it is this additional key that distinguishes a <code
+have a "< >" key: it is this additional key that distinguishes a <code
style="other">pc102</code> keyboard from a <code style="other">pc101</code>
keyboard, and a <code style="other">pc105</code> keyboard from a <code
style="other">pc104</code> keyboard.</p>
@@ -1343,7 +1344,8 @@
<p>If there is some other problem with the generated keysyms, consider
asking about it on the <a href="mailto:debian-user@lists.debian.org";>Debian
-Users' mailing list (<debian-user@lists.debian.org>)</a>; if you're not
+Users' mailing list (<code
+class="other"><debian-user@lists.debian.org></code>)</a>; if you're not
subscribed to that mailing list, be sure you ask for personal replies.</p>
<p>If what <code class="command">xev</code> says makes sense to you, and yet
@@ -1356,10 +1358,10 @@
<p>The ways to deal with bad key behavior from clients are as varied as the
clients themselves. The following discussion is relevant to X terminal
emulation programs, specifically <code class="command">xterm</code>. For help
-with other programs, consult the debian-user mailing list. For reasons of
-space, the following discussion delves a bit more into jargon than the rest of
-this FAQ; if you have trouble understanding it, it may be best to turn to
-debian-user for help.</p>
+with other programs, consult the <code class="other">debian-user</code> mailing
+list. For reasons of space, the following discussion delves a bit more into
+jargon than the rest of this FAQ; if you have trouble understanding it, it may
+be best to turn to <code class="other">debian-user</code> for help.</p>
<ul>
<li> <code class="command">xterm</code> might be translating the key events
@@ -2171,43 +2173,42 @@
<p><em>This entry was written by <a href="mailto:maffew@cat.org.au";>Matthew
Arnison</a>.</em></p>
-<blockquote>
- <p>Particular programs seem to be quite sensitive to the security setup in X.
- I think it is when they use PostScript rendering.</p>
+<p>Particular programs seem to be quite sensitive to the security setup in X. I
+think it is when they use PostScript rendering.</p>
- <p>For LyX, the symptoms are that EPS figures do not render (they show up blank)
- and the terminal window you launched LyX from will give a lot of errors like:</p>
+<p>For LyX, the symptoms are that EPS figures do not render (they show up blank)
+and the terminal window you launched LyX from will give a lot of errors
+like:</p>
<pre>Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server</pre>
- <p>I have also had problems with Mathematica 4.x refusing to start at all, with
- similar error messages. Running <kbd>xhost + localhost</kbd> works as a brute
- force solution for Mathematica, but that sacrifices a lot of security.</p>
+<p>I have also had problems with Mathematica 4.x refusing to start at all, with
+similar error messages. Running <kbd>xhost + localhost</kbd> works as a brute
+force solution for Mathematica, but that sacrifices a lot of security.</p>
- <p>The problem is that <code class="command">xauth</code> and <code
- class="command">startx</code> seem to get confused with old cookies,
- especially if you have changed your machine's hostname or IP address. In
- addition, <code class="command">startx</code> does not have a systematic way
- of cleaning out stale authorisation cookies from your <code
- class="filespec">~/.Xauthority</code>. After you quit X, it cleans cookies
- that it created, but that leaves cookies uncleaned if your computer crashes
- while X is running.</p>
+<p>The problem is that <code class="command">xauth</code> and <code
+class="command">startx</code> seem to get confused with old cookies, especially
+if you have changed your machine's hostname or IP address. In addition, <code
+class="command">startx</code> does not have a systematic way of cleaning out
+stale authorisation cookies from your <code
+class="filespec">~/.Xauthority</code>. After you quit X, it cleans cookies that
+it created, but that leaves cookies uncleaned if your computer crashes while X
+is running.</p>
- <p>So this is what worked for me:</p>
+<p>So this is what worked for me:</p>
- <ul>
- <li>quit X to the console</li>
- <li><kbd>mv ~/.Xauthority ~/.Xauthority.stale</kbd></li>
- <li><kbd>startx</kbd></li>
- </ul>
+<ul>
+ <li>quit X to the console</li>
+ <li><kbd>mv ~/.Xauthority ~/.Xauthority.stale</kbd></li>
+ <li><kbd>startx</kbd></li>
+</ul>
- <p>If <code class="command">startx</code> does not find an <code
- class="filespec">~/.Xauthority</code> file, it will make a fresh one.</p>
+<p>If <code class="command">startx</code> does not find an <code
+class="filespec">~/.Xauthority</code> file, it will make a fresh one.</p>
- <p>I'm not sure how <code class="command">xdm</code> handles <code
- class="filespec">~/.Xauthority</code>. Perhaps it does a better job.</p>
-</blockquote>
+<p>I'm not sure how <code class="command">xdm</code> handles <code
+class="filespec">~/.Xauthority</code>. Perhaps it does a better job.</p>
<h3><a id="startxnonroot">Why am I not able to run <code
class="command">startx</code> as a non-root user?</a></h3>
@@ -2215,15 +2216,12 @@
<p><em>This entry was written by <a href="mailto:walters@debian.org";>Colin
Walters</a>.</em></p>
-<blockquote>
- <p>In the Debian packages of XFree86, some important variables affecting the
- startup of the X server are located in <code
- class="filespec">/etc/X11/Xwrapper.config</code>. In this particular case,
- you must change the option <var>allowed_users</var> to either <code
- class="other">console</code> or <code class="other">anybody</code>. See <code
- class="manpage">Xwrapper.config(5)</code> for more information and
- examples.</p>
-</blockquote>
+<p>In the Debian packages of XFree86, some important variables affecting the
+startup of the X server are located in <code
+class="filespec">/etc/X11/Xwrapper.config</code>. In this particular case, you
+must change the option <var>allowed_users</var> to either <code
+class="other">console</code> or <code class="other">anybody</code>. See <code
+class="manpage">Xwrapper.config(5)</code> for more information and examples.</p>
<h3><a id="confmanagment">How do the XFree86 packages manage their non-conffile
configuration files like <code class="filespec">/etc/X11/X</code>, <code
@@ -2608,7 +2606,7 @@
However, the advice in this section is intended for all dual-head ATI Radeon
users.</p>
-<p>In your <code class="filename">/etc/X11/XF86Config-4</code> file, you may
+<p>In your <code class="filespec">/etc/X11/XF86Config-4</code> file, you may
need to use the <code class="other">MonitorLayout</code> option in each of the
<code class="other">Device</code> sections corresponding to the "heads"
(monitors) being driven by the video card. This option is documented in the
Reply to: