After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613930 - empathy incorrectly updates our own IRC nick for /me
empathy incorrectly updates our own IRC nick for /me
Status: RESOLVED FIXED
Product: empathy
Classification: Core
Component: Multi User Chat
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
: 614178 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-03-25 17:00 UTC by Travis Reitter
Modified: 2011-08-29 10:12 UTC
See Also:
GNOME target: 2.30.x
GNOME version: 2.27/2.28


Attachments
http://git.collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/update-self-user-613930 (515 bytes, patch)
2010-03-26 11:00 UTC, Guillaume Desmottes
accepted-commit_now Details | Review

Description Travis Reitter 2010-03-25 17:00:04 UTC
The /nick command seems to work properly, but if it's followed up with a /me command, our own nick is displayed improperly for us (though correctly for others using Empathy in the same IRC channel).

Example:

/nick pun
=>  - treitter is now known as pun

/me ishment for wjt
=>  * treitter ishment for wjt

The last line should show up as " * pun ishment for wjt"
Comment 1 Guillaume Desmottes 2010-03-26 10:34:52 UTC
Actually it only display your old nick even with normal messages.
Comment 2 Guillaume Desmottes 2010-03-26 11:00:02 UTC
Created attachment 157148 [details] [review]
http://git.collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/update-self-user-613930

 libempathy/empathy-tp-chat.c |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)
Comment 3 Guillaume Desmottes 2010-03-29 08:56:07 UTC
*** Bug 614178 has been marked as a duplicate of this bug. ***
Comment 4 Travis Reitter 2010-03-29 15:16:30 UTC
Review of attachment 157148 [details] [review]:

I haven't tested this, but it looks fine to me.
Comment 5 Guillaume Desmottes 2010-03-29 15:26:53 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.

Will be in 2.30.1