public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-amd64] Eterm wierdness
@ 2007-03-30 15:47 Jason
  2007-03-31  3:54 ` [gentoo-amd64] " Duncan
  0 siblings, 1 reply; 2+ messages in thread
From: Jason @ 2007-03-30 15:47 UTC (permalink / raw
  To: gentoo-amd64

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

* [gentoo-amd64]  Re: Eterm wierdness
  2007-03-30 15:47 [gentoo-amd64] Eterm wierdness Jason
@ 2007-03-31  3:54 ` Duncan
  0 siblings, 0 replies; 2+ messages in thread
From: Duncan @ 2007-03-31  3:54 UTC (permalink / raw
  To: gentoo-amd64

Jason <gentoo@lakedaemon.net> posted 460D3124.6030901@lakedaemon.net,
excerpted below, on  Fri, 30 Mar 2007 11:47:48 -0400:

> 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.

I've no clue on eterm (konsole user here), but have you tried the "reset" 
command, possibly after setting the $TERM environmental variable if 
appropriate?  This usually does the trick if the terminal gets messed up 
catting a binary file or some such.  See the tset/reset manpage for more 
details.  Also, konsole has a built-in reset function accessible from its 
menus, which seems to work, but I'm not sure if it does the same thing or 
works differently.  Of course, I've no clue if eterm has similar.

If that's not it, hopefully someone else can help, as it looks to be out 
of my league.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-03-31  3:56 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-30 15:47 [gentoo-amd64] Eterm wierdness Jason
2007-03-31  3:54 ` [gentoo-amd64] " Duncan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox