From nobody@FreeBSD.org  Wed Dec 18 21:08:02 2013
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hub.freebsd.org (Postfix) with ESMTPS id 2E32F835
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 Dec 2013 21:08:02 +0000 (UTC)
Received: from oldred.freebsd.org (oldred.freebsd.org [IPv6:2001:1900:2254:206a::50:4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.freebsd.org (Postfix) with ESMTPS id 18A811464
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 Dec 2013 21:08:02 +0000 (UTC)
Received: from oldred.freebsd.org ([127.0.1.6])
	by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id rBIL81Ul099429
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 Dec 2013 21:08:01 GMT
	(envelope-from nobody@oldred.freebsd.org)
Received: (from nobody@localhost)
	by oldred.freebsd.org (8.14.5/8.14.5/Submit) id rBIL81HA099421;
	Wed, 18 Dec 2013 21:08:01 GMT
	(envelope-from nobody)
Message-Id: <201312182108.rBIL81HA099421@oldred.freebsd.org>
Date: Wed, 18 Dec 2013 21:08:01 GMT
From: Adrian Chadd <adrian@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: dhclient hostname changes can invalidate xauth sessions
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         184978
>Category:       bin
>Synopsis:       dhclient(8): 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:  Wed Apr 16 01:06:13 UTC 2014
>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:
