On Wednesday 08 February 2006 08:22 am, Dale Harvey wrote:
loudmouth .17 -> when I click connect to server, enter my details (I use my gristle.org account) when I click connect, the status bar changes to establishing connection, but then inkscape crashes, the dialogue does go away, when i move it the canvas behind stays black, eventually everything dissapears, after pressing ctr+c the following shows ( I ented Dale3@...896... in the dialogue, I assumed thats the right format) ** (inkscape:6265): WARNING **: Null recipient JID specified; not sending message.
Ahh...The connection dialog may be misleading: you don't need to enter your full JID for your username, as Inkboard constructs it from the server and username fields. All you need there is the name you registered with, i.e. Dale3. (This strategy does falls apart for some services, like Google Talk, where the server specified in the JID isn't the server you actually connect to; it'll probably need to be changed.)
loudmouth 1.0.1 -> I connect fine, when i choose invite user to share, inkscape crashes, with a generic "inkscape has encountered an internal problem and will close now" QPixmap: Invalid pixmap parameters QPainter::begin: Cannot paint null pixmap QPainter::setPen: Will be reset by begin() QPainter::setBrush: Will be reset by begin() QPainter::setBrush: Will be reset by begin() QPainter::setPen: Will be reset by begin()
Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Segmentation fault
is printed to shell
Interesting. I'm not sure what the Qt errors are doing there, though -- as far as I know, none of Inkscape's components use Qt, and I don't think anything in Loudmouth, or its dependencies, use Qt either...though I could be wrong about that. Maybe they're entirely unrelated to Inkscape, and are being thrown by some other process.
Can you replicate this behavior with a debug build and provide a backtrace? I'm using Loudmouth 1.0.1 myself, and have not experienced this crash situation.
loudmouth 1.0 -> no crashes !, I click invite to user, enter the user, it says its sending it, but the message is discarded in the message_handler, i get 3 messages, "message recieved in invalid context, discarding message"
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'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 do believe somone in glasgow university is doing a paper on undo / redo in a conflict resolution envoiroment though
I'd be interested to see that paper, as well.
Thanks
Dale Harvey
- David