[openbox] aterm causes hourglass on load?

Bryan Alves fryguy at fryguy.dynamixservers.com
Tue May 4 13:16:50 EDT 2004


Ok, aterm maps it's window, and here's some more revelations based on
the suggestions below.

Launching a term from a location where I can see it's stdout shows no
messages at all, but there is no hourglass effect.  The only time I get
hourglass is when launching it from the icon in gnome-panel.  No
messages in .xsession-errors (although I'm not using a session manager,
so I don't think anything would be here).

Also, when transparency is on, windows after the first eventually
totally grey out.  Aterm will map it's window correctly the first time,
then after  few movements/resizes, seemingly random, the aterm will grey
out (grey background instead of transparent).  It seems to be in
relation to drawing over other windows (when it's moved/resized over
another window or vice-versa).  This _only_ happens under openbox, which
is confusing. This only happens after the first aterm (the first is
fine)

The second (and consecutive aterms), if launched from the gnome-panel,
generate the hourglass.  If launched from another terminal, there is no
error.  Also, if launched from the openbox menu, there is no hourglass.

So, to summarize.

-The hourglass only appears when aterm is launched from my gnome panel,
and not from another terminal or the openbox menu
-It'll apply to every aterm run (first, second, and afterwards)
-After the first aterm instance, aterm's background will grey out and
become unreadable, in relation to moving/resizing interactions with
other windows (moving/resizing over/under another window).  Seems to
also happen randomly on occasion

On Tue, 2004-05-04 at 02:47, Marc Wilson wrote:
> On Mon, May 03, 2004 at 05:10:53PM -0400, Bryan Alves wrote:
> > 	My problem is that when doing this, aterm (and only aterm) version
> > 0.4.2 causes an hourglass to appear for a period of approximately 30
> > seconds when executed, and then the hourglass disappears.
> 
> What is *aterm* doing while this is going on?  Does it map its window?  If
> you launch it from another *term so you can see its stdout, does it have
> anything to say?  Does anything appear in ~/.xsession-errors?
> 
> Once aterm has done this once, does another aterm cause it to happen again?
> If you close all aterm(s), then open a new one, does it happen again?




More information about the openbox mailing list