<p class="MsoNormal">At the very least I feel there should be an option to allow
dpkg-reconfigure to run on its own.<br>
<br>
P.S. - I also have always felt that /etc/default/rcS should have:<br>
<br>
FSCKFIX=yes<br>
<br>
So that it that any errors found will be fixed automatically. <br>
<br>
Getting strange errors when booting up, whether they are from Xorg or whatever,
are generally a frightening experience for any user, but must be absolutely
horrifying for someone new...</p>
Just my 2 cents.<br>
<br><div><span class="gmail_quote">On 3/28/06, <b class="gmail_sendername">Rocco Stanzione</b> <<a href="mailto:grasshopper@linuxkungfu.org">grasshopper@linuxkungfu.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tuesday 28 March 2006 14:16, Andy wrote:<br>> If the X server is unable to start, you get a horrid looking error message<br>> which offers to show a log file incomprehensible to 99% of the population<br>> (see my picture:
<a href="http://i1.tinypic.com/sfulab.jpg">http://i1.tinypic.com/sfulab.jpg</a> ).<br>><br>> Instead perhaps we could show a friendly error message, and offer to try<br>> and guess a safe configuration (or perhaps just run dpkg-reconfigure)?
<br>><br>> Unfortunately commands like dpkg-reconfigure or editing a file named<br>> /etc/X11/xorg.conf aren't obvious to non-geeks, especially if the GUI is<br>> broken so you can't search for help (and worse still typing help on the
<br>> command line brings up 'help' for bash rather than the general system!)<br>><br>> Regards, and congrats on a fine distro.<br>><br>> Andy (hope I posted this to the right list!)<br>><br>> one more thing - an error suggesting that 'no screens could be found' seems
<br>> extremely odd to a non-techie user - I mean that message is itself<br>> displayed on the screen, isn't it?! ;)<br><br>I don't know that we should be mucking with Xorg code to friendly up the error<br>messages, but I agree that a failure of X must be incredibly frustrating to
<br>someone who doesn't know what to do about it, and the error messages it<br>provides aren't especially helpful to anyone who hasn't seen them often<br>enough to know what they really mean. Is it feasible to create a wrapper
<br>around X that can capture this output and present to the user some more<br>useful information? For example, it could grep /var/log/Xorg.$DISPLAY.log<br>for (EE) lines, check dmesg for video-related messages, perhaps lint-check
<br>xorg.conf, etc. or even fall back (as previously discussed) to a vesa config<br>for troubleshooting in a friendlier environment.<br><br>Rocco Stanzione<br><br>--<br>ubuntu-devel mailing list<br><a href="mailto:ubuntu-devel@lists.ubuntu.com">
ubuntu-devel@lists.ubuntu.com</a><br><a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel">https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br>+ Nick