Chat error message: can't read "dlgstate(w)": no such variable

Bug #745102 reported by v_2e
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Coccinella
New
Undecided
Unassigned

Bug Description

  I have encountered the strange error messages and behaviour recently trying to chat with one of my jabber contacts. When this person sends me a chat message, I get an empty (though there is quite long chat history for this contact) chat window and an error message window with the following content:

Hook newChatMessageHook failed: 1
can't read "dlgstate(w)": no such variable
    while executing
"set w $dlgstate(w)"
    (procedure "::Chat::GotMsg" line 92)
    invoked from within
"::Chat::GotMsg {message {from <email address hidden>/laptop id ab1ba xml:lang ru-UA type chat to <email address hidden>/Coccinella"
    ("eval" body line 1)
    invoked from within
"eval $func $args"
can't read "dlgstate(w)": no such variable
    while executing
"set w $dlgstate(w)"
    (procedure "::Chat::GotMsg" line 92)
    invoked from within
"::Chat::GotMsg {message {from <email address hidden>/laptop id ab1ba xml:lang ru-UA type chat to <email address hidden>/Coccinella"
    ("eval" body line 1)
    invoked from within
"eval $func $args"

Revision history for this message
buzzdee (sebastia) wrote :

do you get the error every time you get a message from this contact?
do you use separate chat windows or tabbed chat windows?

Changed in coccinella:
milestone: none → 0.96.22
Revision history for this message
v_2e (v-2e) wrote :

No, sometimes I get the chat messages from this contact successfully.
I use tabbed chat window. Is it possible to use different chat windows for different conversations actually?

Revision history for this message
buzzdee (sebastia) wrote :

In preferences -> Appearance you can switch "Use tabbed interface" on and off.

I tried to reproduce the issue with both tabbed and non tabbed interface, but with both I was unable to get the error message. So due to your question I guess you use the tabbed interface.

Do you have any chat window open when you receive the error message when you get that error, or is coccinella opening a new window? When you have a chat window open, is there already a tab open for this contact, or is coccinella trying to open a new tab? In case there is a tab already, is it the active tab when you receive the error message?

Revision history for this message
v_2e (v-2e) wrote :

It happened several times under different circumstances.
1. I had no chat windows opened. That person sent me a chat-message. I got an error message, pressed "OK" and heard an incomming chat-message sound. After that an *empty* chat window opened. No messages from history and no newly sent messages.
2. I had a chat window opened with one or two tabs. Then that same person sent me a chat message. I got an error message, pressed "OK", heard the incoming chat message sound and then a new tab for this new conversation appeared. It was empty.

I must note, that in any case, I can use this empty chat window to send the chat messages to my contact. And he gets those messages. But once this error occured, I cannot see any messages from that person until Coccinella restart. But it does not always work after a restart.

And by the way, I have a pretty long chat history with this contact (for a couple of years or so) and this is the first time such error occurs.

Revision history for this message
buzzdee (sebastia) wrote :

hrm, I love those bugs I cannot reproduce ;)

do you can move the chat history file out of the way, just to see whether this is the cause of the trouble then, and report back?

Revision history for this message
buzzdee (sebastia) wrote :

btw, which version are you using, I guess the latest release or a breakfast build?

Revision history for this message
v_2e (v-2e) wrote :

Yes, I can remove the history file for the experiment purity. But it works correctly right now, so I'll wait for the next error case and then report back if it happens.

I use Coccinella 0.96.21.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.