On 12:28 30 Dec 2002, Kyle <kyle_at_actarg.com> wrote:
| If I do:
|
| export DISPLAY=hostname:0.0
|
| then I can launch programs from the shell window (via tcp), but if I
| again do:
|
| export DISPLAY=:0
|
| It still fails. So its like unix access to the server doesn't work, but
| tcp access still does.
Check to see if the unix socket is still there:
% ls -la /tmp/.X11-unix
total 32
drwxrwxrwt 2 root cameron 4096 Dec 29 14:50 .
drwxrwxrwt 294 root root 28672 Jan 1 12:51 ..
srwxrwxrwx 1 root cameron 0 Dec 29 14:50 X0
Maybe some overly helpful /tmp cleaning program has removed it.
How precise is that "two weeks" time measurement? Like clockwork,
or just touchy-feely?
| If I try to restart fvwm, the session crashes and I have to log back in
| again. Then the session works for a number of days again and then
| mysteriously fails again.
Work around it in your .xsession (or .xinitrc, depending) by setting
$DISPLAY there.
| I thought of always starting fvwm with -d hostname:0.0, but no luck. It
| still forces the DISPLAY variable to :0.0.
More likely it doesn't touch the $DISPLAY variable at all. So all your
subprograms are using :0.0 while fvwm is using hostname:0.0.
| Besides, the unix connection
| is supposed to be more efficient so it would be nice if I could get it
| to work.
Indeed.
| I don't know if this is an fvwm or an X problem but I wanted to see if
| anyone else had seen it or knows what it is. And I don't think I've
| ever seen it on a stock (gnome) redhat box.
See if my /tmp cleaning idea holds.
Cheers,
--
Cameron Simpson, DoD#743 cs_at_zip.com.au http://www.zip.com.au/~cs/
The revolution will not be televised. - Mike Mitten, gnome_at_pd.org, DoD#522
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Dec 31 2002 - 19:56:15 GMT