Bug 16998

Summary: Eterm fails to function from Gnome/Enlightenment pop-up menu
Product: Ports & Packages Reporter: yaldabaoth <yaldabaoth>
Component: Individual Port(s)Assignee: freebsd-ports (Nobody) <ports>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description yaldabaoth 2000-02-26 03:00:04 UTC 
(I think this relates to the "Eterm will not run properly when executed from Bourne shell problem I have seen elsewhere. The errors are the same.)

When running eterm,  the prompt appears as normal. However, whenever I
strike
return, the message "load: 0.16 cmd:csh 87509 [tty1n] 0.03u 0.02s 0%
264k" is
displayed. (The specific PID, load and usage numbers vary, but the
message
is always of the same type.) 

Nothing can be executed from the command line.

Fix: 

Unknown.

(Don't use eterm?)
How-To-Repeat: Unknown. I am running GNOME with Enlightenment, with KDE 
compatibility turned on. I am unsure what other factors may have
some bearing on this.
Comment 1 ade 2000-02-27 16:30:44 UTC 
Take a look at:

http://www.freebsd.org/cgi/query-pr.cgi?pr=16246

Specifically, are you running Eterm 0.8.10?

I have a whole mess (150+) of various xterms, eterms, gnome-terminals
and other junk running on this box right now, with no such problems.

There were issues with previous versions of Eterm.

-aDe

-- 
Ade Lovett, Austin, TX.
Comment 2 yaldabaoth.geo 2000-03-25 05:50:01 UTC 
I think I found the problem. Or at least, can clarify the problem.

I was running Gnome as root while setting up the box. Obviously it was
running in Bourne shell. So, rather than a GNOME/Enlightenment problem,
I think this is related to the "Eterm executed from Bourne shell"
problem posted elsewhere.

Sorry for the lack of that important detail.

Also, FYI, running eterm "out-of-the-box" for 3.4. Don't have the
machine at hand to give a specific version. (Running 3.3 at home.)

AGS


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
Comment 3 Jim Mock freebsd_committer freebsd_triage 2000-07-13 21:40:15 UTC 
State Changed
From-To: open->closed

According to the audit trail, the originator seems to have figured this 
out.  If you have not, please try with updated versions of the ports 
involved.  Lots has changed in the GNOME world since February and March.