apple@nprdc.navy.mil (Jim Apple) (08/22/90)
I have a question about xrooms, what does this message tell me "Warning: app Seashore waiting for a change (0x1)" Does it mean xrooms is having a problem deiconifying this window ?? Seashore is just a xterm. Thanks Jim Apple apple@nprdc.navy.mil WB1DOG ...}ucsd!nprdc!apple
erik@westworld.esd.sgi.com (Erik Fortune) (08/23/90)
In article <9188@arctic.nprdc.arpa>, apple@nprdc.navy.mil (Jim Apple) writes: > "Warning: app Seashore waiting for a change (0x1)" This means that xrooms lost an event or that the window manager didn't do what xrooms asked it to. Whenever xrooms tells an application to change state or to move, it looks for the corresponding events to come back. If the event doesn't show up after a while, xrooms prints that error message and continues. 0x1 is a state change, so it means that xrooms is either losing a property notify or it is unable to iconify (or deiconify) a window. This happens most frequently with non-ICCM compliant window managers. Which window manager are you using? If your connection is slow, the problem could be a lost event. This might cause xrooms to get confused about the state you want for your application. When the event finally does show up, xrooms can no longer identify as the result of something that it did and instead assumes the change was the result of something the user did. If it happens once, you can probably safely ignore it or restart xrooms. If you get this a lot, something else is going on. Tell me a little more about your environment, and maybe I can help track it down. -- Erik (erik@sgi.com)
meo@rsiatl.UUCP (Miles ONeal) (08/25/90)
erik@westworld.esd.sgi.com (Erik Fortune) writes: |In article <9188@arctic.nprdc.arpa>, apple@nprdc.navy.mil (Jim Apple) writes: |> "Warning: app Seashore waiting for a change (0x1)" |This means that xrooms lost an event or that the window manager didn't do |what xrooms asked it to. Whenever xrooms tells an application to |change state or to move, it looks for the corresponding events to come |back.... |This happens most frequently with non-ICCM compliant window managers. |Which window manager are you using? I have had this problem occur when I started xrooms before my window manager. Starting mwm first relegated it to the nearly never happens category. I still get lots of BadWindow events on the server, but they don't seem to affect anything. BTW, could someone who has xrooms working with twm under R3 mention in detail what you do to get it to work? Thanks, Miles