>
> note it is a warning, not an error.  What is actually happening is the
> bblaunch code is rather sloppy.  The fix is easy.
>
> The reason it is complaining is because it tries to read its own window
> which does not have all of the hints set.
>
> The message is spurious anyways.  What is actually happening is the string
> bblaunch is looking for does not exist, but the function it calls returns 0
> for any failure so it thinks it is out of memory.


I realize now I forgot to mention, the application does start, but in the 
wrong workspace.  That doesn't seem to work on some applications.

???



A

Reply via email to