FVWM Bug Tracking notification

new message incoming/1339

Message summary for PR#1339
        From: [EMAIL PROTECTED]
        Subject: Disconnects from X Server on Mac OSX
        Date: Sat, 3 Jul 2004 14:49:23 -0500
        0 replies       0 followups

====> ORIGINAL MESSAGE FOLLOWS <====

>From [EMAIL PROTECTED] Sat Jul 03 14:49:23 2004
Received: from lserv00.math.uh.edu ([129.7.128.99])
        by util2.math.uh.edu with esmtp (Exim 4.30)
        id 1BgqVn-00081w-Oe
        for [EMAIL PROTECTED]; Sat, 03 Jul 2004 14:49:23 -0500
Received: from localhost (lserv00.math.uh.edu [127.0.0.1])
        by lserv00.math.uh.edu (8.11.6/8.11.1) with ESMTP id i63JnNJ24397
        for <[EMAIL PROTECTED]>; Sat, 3 Jul 2004 14:49:23 -0500
Date: Sat, 3 Jul 2004 14:49:23 -0500
Message-Id: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Disconnects from X Server on Mac OSX

Full_Name: Chad Wingrave
Version: 2.4.15
CVS_Date: 
OS: Mac OSX 10.3.4
X_Server: Apple's X11
Submission from: (NULL) (198.82.174.175)


After a period of time, or especially after I move my laptop home, use it
there and return to the lab network (both wireless), I am unable to open
any new X items saying unable to connect to X server.  When using Apple's
window manager, there is not the same problem.  I'm guessing it gets
connected as the hostname changes.  The problem is that it does not always
fail.  When I come back to the lab, I know the DHCP hostname it gives my
machine is always the same and I am assuming the same at home but I can not
be certain (have not checked).

Anyway, it is annoying to have to close all my window's (i'm one of those
guys that likes many xterms open), restart the X server and then reopen all
my windows.  I've tried restartting fvwm2 but it just crashes (as I assume
it tries to reconnect to the X server and fails).

Any ideas?



--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to