public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason <gentoo@lakedaemon.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Eterm wierdness
Date: Fri, 30 Mar 2007 11:47:48 -0400	[thread overview]
Message-ID: <460D3124.6030901@lakedaemon.net> (raw)

Got a wierd one. Sometimes (usually after a memory intensive task, like 
emerging ooffice), Eterms in which I'm logged in as root will cause a 
PrintScreen whenever I hit an arrow key.

To avoid the printjobs, I start Eterm with '--print-pipe /usr/bin/true', 
which prevents the waste of paper, but crashes the Eterm.  Once the 
condition trips (after emerging ooffice), it is 100% repeatable.  root 
logins in xterm do _not_ exhibit the same behavior.  User logins in 
either Eterm or xterm don't do it either.

I'm thinking it is some sort of memory access error in bash when 
'TERM=Eterm', but I'm having trouble narrowing it down.  I tried using 
the Eterm.ti file ('tic -o /usr/share/terminfo/ Eterm.ti') from the 
Eterm tarball (Gentoo recently started using the one provided by 
ncurses).  No luck.

If I shut down the X server and restart it, it goes away.

Anyone have a clue where I can look?  I'd like to isolate and fix it so 
I can just provide a patch to the appropriate folks.  For all I know, it 
could be a problem in X or enlightenment...

thx,

Jason.
-- 
gentoo-amd64@gentoo.org mailing list



             reply	other threads:[~2007-03-30 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 15:47 Jason [this message]
2007-03-31  3:54 ` [gentoo-amd64] Re: Eterm wierdness Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=460D3124.6030901@lakedaemon.net \
    --to=gentoo@lakedaemon.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox