On Sat, 08 Mar 2003 09:00:36 -0800
Lars Eggert <[EMAIL PROTECTED]> wrote:

> On 3/7/2003 11:50 PM, Marcel Moolenaar wrote:
> > On Fri, Mar 07, 2003 at 11:30:34PM -0800, Lars Eggert wrote:
> >>
> >>this may be unrelated, but for about ten days or so, I have problems 
> >>where gnometerminal will stop updating after a while. I can still use 
> >>the menus, close it, etc. - but all output is suspended. Most of the 
> >>time, selecting "Reset" from the menu repeatedly will eventually get me 
> >>back to a working state again. It also seems that pasting multi-line 
> >>text into a gnometerminal (as opposed to typing or it displaying output) 
> >>will trigger this frequently.
> > 
> > <AOL>Me too</AOL>
> > 
> > I tend to think it happens more often with maximized windows than
> > not and also when long lines are involved. A reset most of the time
> > gets me back, but I do occasionally have to kill gnome-terminal
> > completely when all the terminals are dead. Unfortunately I don't
> > have the time to dig into it, but I'm probably going to switch
> > window manager and see if that makes a difference. For some reason
> > I'm suspicious about Metacity. Not necessarily because of this...
> 
> I also switched to a TrueType font for gnometerminals (bitstream-vera) 
> around the same time, so maybe that's a factor, too.
> 
> As for window managers, I use sawfish (and have been, for a long time 
> before the problem.)
> 
> Also (unrelated?), it seems that X eats up a LOT of CPU with antialiases 
> TrueType fonts in terminals, compared to good, old lucida-typewriter.

"Fatal server error:  xf86OpenConsole: VT_SETMODE VT_PROCESS failed"

You could try rebuilding gnometerminal and use the 'WITH_ZVT' 
option. This is a workaround for some gnometerminal funkyness 
that was discussed in the freebsd-gnome list. Font functions 
are lost, but speed, resource usage, and highlighting for 
copy/paste is improved.

Regards,

Stephen Hilton
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to