From: Antonio Vargas <wind@cocodriloo.com>
To: James Strandboge <jamie@tpptraining.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: odd gnome-terminal behavior in 2.5.67-mm3
Date: Fri, 25 Apr 2003 15:06:09 +0200 [thread overview]
Message-ID: <20030425130609.GI6009@wind.cocodriloo.com> (raw)
In-Reply-To: <1051277058.1588.70.camel@sirius.strandboge.cxm>
On Fri, Apr 25, 2003 at 09:24:18AM -0400, James Strandboge wrote:
> On Thu, 2003-04-24 at 15:26, David Mansfield wrote:
> > Hi Andrew, list
> >
> > I've been experiencing some odd behavior running 2.5.67-mm3 on my RH9
> > based desktop.
> >
> > It's probably an application bug, but something strange is happening
> > anyway that doesn't happen in 'stable' kernels.
> >
> > What happens is that gnome-terminal gets stuck in some sort of 'infinite
> > loop' when a lot of output is going to the screen and also keypresses are
> > going in (like paging through a large file - holding down pgup/pgdown).
> >
> > Xterm doesn't seem to be affected.
>
> I'll chime in and mention that I've seen this too, and also doing a
> paste operation via highlight and middle click doesn't work in 2.5
> either. I assumed it was a libvte bug.
I've experienced this also when running "make menuconfig"
against 2.5.66 while running 2.5.66 on a redhat9 system.
I filled a bug-report on bugzilla.rehat.com and
they told me "bug is reproduced here. workaround is to
minimize the gnome-terminal while there is intense
terminal activity"... so I'm supposed to config my
kernel while it's terminal is not visible... great :)
I'd not mind trying to debug gnome-terminal if
I didn't need to install bazillons of libs
for his recompile...
prev parent reply other threads:[~2003-04-25 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 19:26 odd gnome-terminal behavior in 2.5.67-mm3 David Mansfield
2003-04-25 13:24 ` James Strandboge
2003-04-25 13:06 ` Antonio Vargas [this message]
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=20030425130609.GI6009@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=jamie@tpptraining.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).