>Number: 184978 >Category: bin >Synopsis: dhclient hostname changes can invalidate xauth sessions >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 18 21:10:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Adrian Chadd >Release: -HEAD >Organization: >Environment: N/A - applies to 9.x, 10.x, 11.0 >Description: The hostname (re)setting via dhclient-script seems to cause the whole xauth session to suddenly be invalid. This prevents new X applications from starting.
In a world where one can't just restart the X server without rebooting, this is a bit of a problem. >How-To-Repeat: Start an xauth session, then jump on a network whose DHCP server resets the hostname for you. >Fix: Changing the hostname back to the original hostname fixes things. I don't know whether disabling the hostname setup via dhclient is the right thing to do but it seems the only thing that works for me. >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
