Re: sawfish has lost a window - window is found with xdotool



Timo Korvola said:     (by the date of Tue, 2 Nov 2010 20:54:33 +0200)

> On Tuesday 02 November 2010 07:47:50 Teika Kazura wrote:
> > On Tue, 26 Oct 2010 01:10:42 +0200, Janek Kozicki wrote:
> > >   Map State: IsUnviewable
> > 
> > Does this mean it got unmapped?
> 
> The window itself is mapped but an ancestor is unmapped [see 
> XGetWindowAttributes(3)]. Top level windows don't have many ancestors, 
> normally just the window frame created by Sawfish and the root window, 
> which is always mapped. The output from xwininfo -root -tree would 
> suggest that 0xc01020 is the window frame; Janek could check whether it 
> is mapped with xwininfo -id 0xc01020.

There you go:

janek atak:~$ xwininfo -all -id 0xc01020

xwininfo: Window id: 0xc01020 (has no name)

  Root window id: 0x2a0 (the root window) (has no name)
  Parent window id: 0x2a0 (the root window) (has no name)
     17 children:
     0xc11b0d (has no name): ()  16x16+560+2  +-21520+687
     0xc11b0b (has no name): ()  16x16+544+2  +-21536+687
     0xc11b09 (has no name): ()  16x16+528+2  +-21552+687
     0xc11b07 (has no name): ()  2x199+576+18  +-21504+703
     0xc11b05 (has no name): ()  2x2+576+217  +-21504+902
     0xc11b03 (has no name): ()  574x2+2+217  +-22078+902
     0xc11b01 (has no name): ()  2x2+0+217  +-22080+902
     0xc11aff (has no name): ()  2x199+0+18  +-22080+703
     0xc11afd (has no name): ()  2x16+574+2  +-21506+687
     0xc11afb (has no name): ()  2x18+576+0  +-21504+685
     0xc11af9 (has no name): ()  2x18+0+0  +-22080+685
     0xc11af7 (has no name): ()  16x16+2+2  +-22078+687
     0xc11af5 (has no name): ()  16x16+18+2  +-22062+687
     0xc11af3 (has no name): ()  3x16+525+2  +-21555+687
     0xc11af1 (has no name): ()  3x16+34+2  +-22046+687
     0xc11aef (has no name): ()  488x16+37+2  +-22043+687
     0xc11aed (has no name): ()  574x2+2+0  +-22078+685

  Absolute upper-left X:  -22080
  Absolute upper-left Y:  685
  Relative upper-left X:  -22080
  Relative upper-left Y:  685
  Width: 578
  Height: 219
  Depth: 24
  Visual: 0x21
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x20 (installed)
  Bit Gravity State: ForgetGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsUnMapped
  Override Redirect State: yes
  Corners:  +-22080+685  -26622+685  -26622-296  +-22080-296
  -geometry 578x219+-22080+685

  Bit gravity: ForgetGravity
  Window gravity: NorthWestGravity
  Backing-store hint: NotUseful
  Backing-planes to be preserved: 0xffffffff
  Backing pixel: 0
  Save-unders: No

  Someone wants these events:
      KeyPress
      ButtonPress
      ButtonRelease
      EnterWindow
      LeaveWindow
      PointerMotionHint
      ButtonMotion
      Exposure
      VisibilityChange
      SubstructureRedirect
      FocusChange
  Do not propagate these events:
  Override redirection?: Yes

  No window manager hints defined

  No normal window size hints defined
  No zoom window size hints defined

  Window shape extents:  574x199+2+18
  No border shape defined


... but I got a bit lost here. I have already recovered my lost
window, so I guess that status mapped/unmapped of 0xc01020 is fixed
altogether. 

I wish I had a result of this command `xwininfo -all -id 0xc01020`
_before_ window was found.

 
> It would appear that the managed window list has become corrupt: if 
> Sawfish has framed the window, it should be on the list and retrievable 
> with get-window-by-*.

So you mean - trying to access 0xc01020, instead of 0x3000024 ?

(setq foo (get-window-by-id 0xc01020))

It's worth remembering for future - next time I'll be able to debug
this better.

-- 
Janek Kozicki                               http://janek.kozicki.pl/  |


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]