On Tue, Aug 08, 2006 at 07:38:49PM +0900, Carsten Haitzler wrote:
> On Tue, 8 Aug 2006 12:11:30 +0200 Toby Cubitt <[EMAIL PROTECTED]> babbled:
>
> > In recent CVS checkouts of enlightenment 17, bits of window
> > occasionally seem to be left behind, either when changing virtual
> > desktop, or when an X-client terminates.
>
> can you do an xprop on the window?
xprop doesn't return anything when I click on the ghost window.
> find out its window id and where it is in the window tree (xwininfo
> -tree -root - provide a screenshot yoo)
xwininfo does give output when I click on the ghost:
************************************************************
xwininfo: Please select the window about which you
would like information by clicking the
mouse in that window.
xwininfo: Window id: 0x8000a1 (has no name)
Absolute upper-left X: 0
Absolute upper-left Y: 0
Relative upper-left X: 0
Relative upper-left Y: 0
Width: 490
Height: 660
Depth: 24
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0x20 (installed)
Bit Gravity State: NorthWestGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsViewable
Override Redirect State: yes
Corners: +0+0 -534+0 -534-108 +0-108
-geometry 490x660+0+0
************************************************************
Here's the output of "xwininfo -tree -root":
************************************************************
xwininfo: Window id: 0x44 (the root window) (has no name)
Root window id: 0x44 (the root window) (has no name)
Parent window id: 0x0 (none)
20 children:
0x800021 (has no name): () 1x1+-100+-100 +-100+-100
0x80001c "Enlightenment Black Zone (0)": ("E" "Black_Window")
1024x768+0+0 +0+0
0x800017 (has no name): () 1x1+0+0 +0+0
0x80001b (has no name): () 1022x1+1+767 +1+767
0x800019 (has no name): () 1x768+1023+0 +1023+0
0x800018 (has no name): () 1x768+0+0 +0+0
0x80001a (has no name): () 1022x1+1+0 +1+0
0x800016 (has no name): () 1x1+0+0 +0+0
0x800015 (has no name): () 1x1+0+0 +0+0
0x800014 (has no name): () 1x1+0+0 +0+0
0x8000b9 (has no name): () 788x587+98+40 +98+40
3 children:
0x8000bf (has no name): () 780x559+4+24 +102+64
1 child:
0x1600002 "Mutt email client": ("mutt" "Eterm") 780x559+0+0 +102+64
2 children:
0x1600014 "Eterm Scrollbar": () 14x312+466+0 +568+64
3 children:
0x1600017 (has no name): () 10x286+2+13 +570+77
0x1600016 (has no name): () 10x10+2+300 +570+364
0x1600015 "Eterm Scrollbar Anchor": () 10x10+2+2 +570+66
0x160000c (has no name): () 780x559+0+0 +102+64
0x8000be (has no name): () 788x587+0+0 +98+40
0x8000ba "Enlightenment Frame": ("E" "Frame_Window") 788x587+0+0
+98+40
0x800013 (has no name): () 1x1+0+0 +0+0
0x8000a1 (has no name): () 490x660+0+0 +0+0
3 children:
0x8000a7 (has no name): () 490x660+0+0 +0+0
0x8000a6 (has no name): () 490x660+0+0 +0+0
0x8000a2 "Enlightenment Frame": ("E" "Frame_Window") 490x660+0+0 +0+0
0x800012 (has no name): () 1x1+0+0 +0+0
0x800023 "E Popup": ("E" "_e_popup_window") 99x40+925+728 +925+728
0x800011 (has no name): () 1x1+0+0 +0+0
0x800007 "Enlightenment Background": ("E" "Background_Window")
1024x768+0+0 +0+0
2 children:
0x800022 (has no name): () 1x37+861+730 +861+730
0x80000b (has no name): () 1024x768+0+0 +0+0
0x800002 (has no name): () 5x5+-200+-200 +-200+-200
0x800001 (has no name): () 123x456+-77+-777 +-77+-777
0x600002 (has no name): () 1x1+0+0 +0+0
************************************************************
There's a new screenshot of the situation more or less as it was when
I produced the xwininfo output (I minimised the Eterm window running
mutt where I'm composing this, so that only the ghost window is
visible) at: www.dr-qubit.org/E17_bug2.png
In case it's any use, I've also put a screenshot of the output
displayed by selecting the "window properties" option from the
right-click menu displayed by clicking on the ghost, at
www.dr-qubit.org/E17_winprops.png
> also does this go away after e restarts?
If I restart e manually, the ghost window is removed, but I still
sometimes see new ghost windows.
> are you using engage? (seems so)
Yes.
> maybe try ibar instead of engaged
I can't reproduce the problem if I unload engage and use ibar
instead. Also, when the ghost window was visible and I disabled
engage, enlightenment segfaulted. Seems like it's an engage issue
then...
My version of engage is also a recent CVS checkout (within the last
week I think).
> ghost windows have been a problem in the past but i have actually
> not seen one in a loooooooooooooooong time - and i only use the
> modules e comes with. was that window a borderless one before too?
The window in the screenshot was borderless and sticky, but I've now
seen the problem with a non-borderless Eterm too (also only when
running engage).
I ought to mention that the Eterm's are using pseudo-transparency (I
set the root window background to the same image as e's background
using Esetroot). I know pseudo-transparency is not supposed to work
reliably, but it always has for me ;-) If that turns out to be the
problem, then feel free to tell me to either stop using it, or go away
and live with the consequences ;-)
> > I've put a screenshot at: www.dr-qubit.org/E17_bug.jpeg
> >
> > Is anyone else seeing this?
Toby
--
PhD Student
Quantum Information Theory group
Max Planck Institute for Quantum Optics
Garching, Germany
email: [EMAIL PROTECTED]
web: www.dr-qubit.org
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
