> I meant to say gtk2-engines or so, probably gtk2-engines-qt.
> But smooth is definitely broken and should be removed on any system.

I just removed the qt-gtk/2-engines and the error is gone, cheers

> Argh, this may be my fault. :P  Now I wish I wrote better error messages...

> That error message means that Inkboard received a message that it was not
> expecting to receive in its current state.  (There's a number of client
> states: disconnected, ready to receive or send whiteboard invitations,
> receiving invitation, in whiteboard, etc.)

I was wondering if the jabber connection is dying pretty quickly, I get the status saying
establishing connection, and then connected to jabber server Server as User, but that status
goes away after a few seconds, Looking closely I just noticed it says connected, for around
10 seconds, then the status says it is again trying to establish a connection(this status is shown
momentarily,it basically flashes too quick to be noticed) then the status
reverts to normal(no objects selected). so thats probably what my problem is

is the error I get

** (inkscape:10938): WARNING **: Received message in incorrect context (currentis not a subset of required); discarding message.

** (inkscape:10938): WARNING **: current context=000001010 required context=000000010 (msgtype CONNECT_REQUEST_USER)

** (inkscape:10938): WARNING **: Default message handler received message in invalid receive context; discarding message.


> I'd like to try Inkboard out with you sometime -- it seems to be the easiest
> way to troubleshoot this.  What times would be best for you?

I try to sit in #inkscape most of the time I am working, i should be on till around 7GMT today,
most of tommorow 11 - 5GMT, and I will be able to make time over the weekend as well, its probably
easier to say when is easier for you, and thanks

> What happens if someone's computer crashes who has a lock on a
> section of the document?  How do users communicate that they
> would like the lock?

I had previously planned over a tcp connection,  so it would be notified when the connection was dropped,
It was also in a more server / client model, similiar to online games, where the computer that started
the session would be the host, it would store a basic object / lock table for quick lookups, the actual lock
request would be be by simply selecting the object, which has the obvious effect on slowing down the interface
on selecting an object, which is what the nested lock was designed to help.