[NCLUG] New to NCLUG

[Ben West]

On Mon, Feb 13, 2012 at 11:56 AM, Bob Proulx <bob at proulx.com> wrote:

> Chad Perrin wrote:
> > I find that when a GUI program is misbehaving, it is often helpful to try
> > starting the application by entering its name at a shell prompt rather
> > than by clicking on something or selecting from a GUI menu.  When doing
> > that, GUI programs that misbehave might give somewhat useful output in
> > the shell sessions from which you launched it.
>
> Agreed.  I always go first to the command line to get good feedback.
>
> For information from the GUI many times this information is placed in
> your ~/.xsession-errors file.  That is a catch-all for all output from
> your X session and is inherited by all of the GUI applications started
> from it.  It usually has a lot of noise in the file since there are a
> lot of noisy GUI programs.  But if you can wade through the noise
> there are often useful errors reported there.  Can be useful.
>
> Bob
> _______________________________________________
> NCLUG mailing list       NCLUG at lists.nclug.org
>
> To unsubscribe, subscribe, or modify
> your settings, go to:
> http://lists.nclug.org/mailman/listinfo/nclug
>

Likewise tail -f ~/.xsession-errors is a great thing to run in a terminal
window; it can show you the errors in real-time