Re: Lindows programs unexpectantly closing
- From: sk8r-365 <sk8r-365@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 29 Jun 2007 07:16:52 -0600
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. Although, if
there's an .xsession-errors file, there may be messages.
--
sk8r-365
http://goodbye-microsoft.com/
.
- Follow-Ups:
- Re: Lindows programs unexpectantly closing
- From: Chris F.A. Johnson
- Re: Lindows programs unexpectantly closing
- References:
- Lindows programs unexpectantly closing
- From: Pete
- Re: Lindows programs unexpectantly closing
- From: beowulf@xxxxxxxxxxxx
- Lindows programs unexpectantly closing
- Prev by Date: Re: Lindows programs unexpectantly closing
- Next by Date: Re: Lindows programs unexpectantly closing
- Previous by thread: Re: Lindows programs unexpectantly closing
- Next by thread: Re: Lindows programs unexpectantly closing
- Index(es):
Relevant Pages
|