Bug 1137

Summary: xterm #196 fix for utmp cleanup
Product: xorg Reporter: Thomas Dickey <dickey>
Component: App/xtermAssignee: Jim Gettys <jg>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: high CC: kem
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 351    
Attachments:
Description Flags
diff between xterm 195 and 196 none

Description Thomas Dickey 2004-08-19 13:34:14 UTC
see http://invisible-island.net/xterm/xterm.log.html
Comment 1 Jim Gettys 2004-08-19 14:06:43 UTC
	From: 	Thomas Dickey <dickey@radix.net>
To: 	Jim Gettys <Jim.Gettys@hp.com>
Subject: 	Re: Is you entry of bug 1137 on fd.o?
Date: 	Thu, 19 Aug 2004 17:04:16 -0400	
On Thu, Aug 19, 2004 at 04:54:34PM -0400, Jim Gettys wrote:
> https://freedesktop.org/bugzilla/show_bug.cgi?id=1137
> 
> A request we should update our bits before we ship for a
> to fix a particular bug?
> 
> If so, making it block (currently) bug 351 will raise it
> as a blocker for our upcoming release...

yes.  It doesn't dump core, or prevent someone from using xterm, but would
cause some heartburn.

The process that's trying to do the cleanup will hang on "real" Unix systems -
infinite loop.

I was told about this on Sunday, and spent several hours finding about the
problem and seeing that the fix is relatively small.  (I tested it on HPUX
and Linux).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
Comment 2 Kevin E. Martin 2004-08-19 21:56:24 UTC
This sounds like it is needed.  Is there a place where we can pick up the patch,
or can a patch be attached here?
Comment 3 Alexandru Fomin 2004-08-20 01:28:40 UTC
Created attachment 689 [details] [review]
diff between xterm 195 and 196

should apply cleanly with something like:

cd [...]/xc/programs/xterm
patch -p1 -i <diff location>
Comment 4 Kevin E. Martin 2004-08-20 11:47:37 UTC
Patch checked in.
Closing.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.