Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Oct 1999 17:48:53 -0700 (PDT)
From:      khuon@FreeBSD.ORG
To:        freebsd-gnats-submit@freebsd.org
Subject:   ports/14337: xdm and Eterm: tty allocation problem?
Message-ID:  <19991015004853.A950614C95@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         14337
>Category:       ports
>Synopsis:       xdm and Eterm: tty allocation problem?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 14 17:50:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     Jake Khuon
>Release:        3.3-RELEASE
>Organization:
Global Crossing Ltd., GlobalCenter Div.
>Environment:
FreeBSD Mocha.NEEBU.Net 3.3-RELEASE FreeBSD 3.3-RELEASE #3: Thu Oct 14 06:32:45 EDT 1999     khuon@Mocha.NEEBU.Net:/contrib/src/sys/compile/MOCHA  i386

>Description:
Running Eterm with /bin/sh from a .xsession via xdm results in an
unusable shell.
>How-To-Repeat:
[1] chsh to /bin/sh or you can skip this part and invoke /bin/sh from step #4

[2] Use the following .xsession:
	#!/bin/sh
	/usr/X11R6/bin/Eterm&	#for testing
	/usr/X11R6/bin/xterm&	#for a usable shell
	/usr/X11R6/bin/twm	#for window management while testing

[3] Login from xdm

[4] Invoke /bin/sh if you didn't reset your default shell.

[5] Try typing in the Eterm window.  This is what I get by
    simply hitting the return key:

	$ load: 0.40  cmd: sh 873 [ttyin] 0.00u 0.00s 0% 360k
	load: 0.37  cmd: sh 873 [ttyin] 0.00u 0.00s 0% 360k
	load: 0.37  cmd: sh 873 [ttyin] 0.00u 0.00s 0% 360k
	load: 0.37  cmd: sh 873 [ttyin] 0.00u 0.00s 0% 360k
	load: 0.37  cmd: sh 873 [ttyin] 0.00u 0.00s 0% 360k

    No commands work either:
	lsload: 0.03  cmd: sh 873 [ttyin] 0.00u 0.00s 0% 360k
	setload: 0.03  cmd: sh 873 [ttyin] 0.00u 0.00s 0% 360k
	clearload: 0.03  cmd: sh 873 [ttyin] 0.00u 0.00s 0% 360k

[6] If you spawn an Eterm from the xterm you also have open,
    everything in the new Eterm works fine.  It only seems to be
    problem with Eterms spawned from xdm or from a WM that was
    started via xdm.

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991015004853.A950614C95>