Open Bug 1059398 Opened 10 years ago Updated 2 years ago

IRC conversation title becomes "undefined" after recipient nick change

Categories

(Thunderbird :: Instant Messaging, defect)

31 Branch
defect

Tracking

(Not tracked)

People

(Reporter: deepanshu2017, Unassigned)

References

(Depends on 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140715214327

Steps to reproduce:

1. Connect to IRC server
2. Join channel
3. PM another user (A new conversation starts)
4. Other user changes nickname



Actual results:

PM conversation changes to "Undefined"

I can hear the sound of his messages and I can message him through "/msg nick message" but I cannot see his message nor I can close that "undefined window". When I try to change my nick the other person got undefined window. Sometimes it happens on first time changing the nick sometimes it happens after 2 times changing the nick so it is not fix but it do happen always. I and my friends specially create 4 users on thunderbird and instantbird but the thunderbird user face the problem only.

I have screenshots and they are 8 in numbers so the link of the screenshots is in the first comment.


Expected results:

The PM conversation should change to the new nick of the other user.
http://1drv.ms/1qhqgTs

The link for the screenshots.
Component: Untriaged → Instant Messaging
Do you see any errors or warnings in the error console that look like they might be related when this happens?
Summary: I have Private message a guy on Thunder Bird IRC and then the converstaion renamed to undefined → I have Private message a guy on Thunderbird IRC and then the converstaion renamed to undefined
OS: Linux → All
Hardware: x86_64 → All
Summary: I have Private message a guy on Thunderbird IRC and then the converstaion renamed to undefined → IRC conversation title becomes "undefined" after recipient nick change
Status: UNCONFIRMED → NEW
Depends on: 954891
Ever confirmed: true
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.