Re: Lindows programs unexpectantly closing
- From: "Chris F.A. Johnson" <cfajohnson@xxxxxxxxx>
- Date: Fri, 29 Jun 2007 13:46:08 -0400
On 2007-06-29, sk8r-365 wrote:
beowulf@xxxxxxxxxxxx said:
Try starting programs from a terminal rather than the GUI menus, then
when they crash you should get some error output from the terminal
that you can share here, which will help diagnose what is happening.
For example, from a terminal you might type 'evolution' or
'evolution&' to run the email program evolution, or 'gimp&' to run the
GIMP image editor (of course do not type the single quotes). The &
added on the end of a command helps it run in multitasking/background
mode.
$ evolution&
$ gimp&
If you use '&' there is little likelihood for output because that
shell will not have that app as a child process.
A background process *is* a child of the shell that spawned it, and
anything it sends to stdout or stderr will appear in that shell.
--
Chris F.A. Johnson, author | <http://cfaj.freeshell.org>
Shell Scripting Recipes: | My code in this post, if any,
A Problem-Solution Approach | is released under the
2005, Apress | GNU General Public Licence
.
- Follow-Ups:
- Re: Lindows programs unexpectantly closing
- From: sk8r-365
- Re: Lindows programs unexpectantly closing
- References:
- Lindows programs unexpectantly closing
- From: Pete
- Re: Lindows programs unexpectantly closing
- From: beowulf@xxxxxxxxxxxx
- Re: Lindows programs unexpectantly closing
- From: sk8r-365
- Lindows programs unexpectantly closing
- Prev by Date: Re: Linux laptop with 2560x1600 graphics
- Next by Date: Re: Linux laptop with 2560x1600 graphics
- Previous by thread: Re: Lindows programs unexpectantly closing
- Next by thread: Re: Lindows programs unexpectantly closing
- Index(es):
Relevant Pages
|