Yes.  I am positive that the alpha blackbox's did not do this--at least
not unmapping ALL the windows that it knew about.  This has bugged me
for quite a while, and it only seems to happen when the "Exit" menu item
is used, at least on my box.  If I do a "killall blackbox", then
blackbox leaves all the windows up (including the windows that were in the
slit before exiting).  But if I do an "Exit" from
the menu, everything that was in the slit (bbkeys, bbpal, gkrellm, etc),
goes buh-bye and does NOT come back when blackbox (or any other window
manager) restarts/starts.  To clarify, the windows are XUnmapWindow'd, but the
programs are still running.  Mind you, this is only minorly annoying, as I
refuse to run anything but blackbox (gosh, 2 years ago, I was flipping
through window managers faster than 2 per week...), but still, when I go
to shut down my system, I normally do an Exit from blackbox's menu, then
wait for my iconified aterm window to come up so I can "shutdown -p
now", but alas, he never does....  

Annoying.  =:)  

And bah humbug!  =:)

But still, blackbox is the best I've seen, so nyz/Raven, keep up the
tremendously great work.

* Jim Knoble <[EMAIL PROTECTED]> [000721 16:22]:
> Under the blackbox-20000627 snapshot (and also under 0.60.3), if i exit
> from Blackbox with a window iconified, the window appears to disappear
> into Limbo.
> 
> By way of clarification:
> 
>   (0) My ~/.xsession starts 'xsession' as the long-lived program.
>       Xsession starts my default window manager (Window Maker).  To
>       start Blackbox, i exit from Window Maker, then choose Blackbox
>       from xsession's "Window Managers" menu.
> 
>   (1) During my Blackbox session, i start an X client, such as
>       'xclipboard', and iconify it.  Xclipboard appears in the Icons
>       submenu of the Workspaces menu.  'ps' sees the xclipboard process:
>       
>         $ ps auxwww |fgrep xclipboard |fgrep -v fgrep
>         jmknoble  9733  0.2  2.6  2884 1676 ?        S    04:20   0:00 xclipboard
>         $ 
> 
>       and 'xprop' sees the window:
>       
>         $ xprop -name xclipboard
>         WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
>         _BLACKBOX_ATTRIBUTES(_BLACKBOX_ATTRIBUTES) = 0x10, 0x0, 0x0, 0x0, 0x0, 0x0, 
>0x0, 0x0
>         WM_STATE(WM_STATE):
>                         window state: Iconic
>                         icon window: 0x0
>         WM_CLIENT_LEADER(WINDOW): window id # 0x3c0001e
>         WM_LOCALE_NAME(STRING) = "C"
>         WM_CLASS(STRING) = "xclipboard", "XClipboard"
>         WM_HINTS(WM_HINTS):
>                         Client accepts input or input focus: True
>                         Initial state is Normal State.
>         WM_NORMAL_HINTS(WM_SIZE_HINTS):
>                         user specified size: 510 by 200
>                         window gravity: NorthWest
>         WM_CLIENT_MACHINE(STRING) = "quipu.half.pint-stowp.cx"
>         WM_COMMAND(STRING) = { "xclipboard" }
>         WM_ICON_NAME(STRING) = "xclipboard"
>         WM_NAME(STRING) = "xclipboard"
>         $             
> 
>   (2) I restart Blackbox using the '[restart]' menu directive.
>       Xclipboard appears briefly on the screen, unmanaged, until
>       Blackbox restarts and begins managing the xclipboard window, at
>       which point xclipboard becomes iconified again (and appears in
>       the Workspaces->Icons submenu in the new Blackbox session).  'ps'
>       still sees the process, and 'xprop' still sees the window.
> 
>   (3) I exit Blackbox (using '[exit]').  All the windows are now
>       unmanaged.  The Xclipboard window, however, doesn't reappear.
>       'ps' still sees the xclipboard process, but 'xprop' can't seem
>       to find the window at all:
>       
>         $ ps auxwww |fgrep xclipboard |fgrep -v fgrep
>         jmknoble  9733  0.0  2.6  2884 1676 ?        S    04:20   0:00 xclipboard
>         $ xprop -name xclipboard
>         xprop: error: No window with name xclipboard exists!
>         $ 
> 
>       If i restart Blackbox, Blackbox is also unable to find the
>       xclipboard window.  Where did it go?
> 
> The same sort of thing happens with bbkeys.  If i start bbkeys from
> within my Blackbox session, then exit Blackbox and start another window
> manager (or start Blackbox again), bbkeys is still running, but its
> window is ... elsewhere.  Nevertheless, bbkeys is still grabbing its
> configured keystrokes, giving rise to strange behaviors until i
> 'killall bbkeys'.
> 
> Unfortunately, the place where this becomes a drastic problem for me is
> when i happen to leave my xsession window iconified at the time that i
> exit Blackbox:  then, my whole X session goes away, and i get to
> login again via xdm.
> 
> I can reproduce this on the following platforms:
> 
>   - Red Hat Linux 6.1, kernel-2.2.14-12 (urp, should upgrade that),
>     egcs-1.1.2, libstdc++-2.9.0, XFree86-3.3.5
>   
>   - Red Hat Linux 5.2, kernel-2.0.38, egcs-1.1.2, libstdc++-2.9.0,
>     XFree86-3.3.5 
> 
> Has anyone else encountered this?  How can i help find the problem and
> fix it?
> 
> -- 
> jim knoble | [EMAIL PROTECTED] | http://www.jmknoble.cx/
> 
> 

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=
Jason Kasper (vanRijn)
Systems     Engineer
bash$ :(){ :|:&};:
VORFA

Reply via email to