"You are now identified for <username>" message doesn't make sense

Bug #692296 reported by Chris Wilson
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Invalid
Low
Unassigned
telepathy-idle (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: empathy

When the user logs into IRC using Empathy, the message "You are now identified for <username>" is presented to the user. This does not make sense, and it should read "You are now identified as <username>".

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :
Changed in hundredpapercuts:
status: New → Confirmed
assignee: nobody → Chris Wilson (notgary)
affects: empathy (Ubuntu) → xchat-gnome (Ubuntu)
Jack Leigh (leighman)
Changed in xchat-gnome (Ubuntu):
status: New → Confirmed
Revision history for this message
Vish (vish) wrote :

Hmm, We dont install xchat-gnome by default nor do I see it listed in the Software Center "Featured Apps"..
Am I missing something here, any reason this was included as a papercut?

Changed in hundredpapercuts:
status: Confirmed → Incomplete
Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

I've probably just marked the wrong application in that case, but whatever application it is that is responsible for signing the user into IRC, or for notifying the user that this has happened, is where the problem lies. I had first thought that it was Empathy itself that was the problem until I came across another bug that referenced this behaviour.

Revision history for this message
Vish (vish) wrote :

telepathy-idle is the package which handles IRC for empathy. [Xchat is a totally different app for IRC.]

affects: xchat-gnome (Ubuntu) → telepathy-idle (Ubuntu)
Changed in telepathy-idle (Ubuntu):
importance: Undecided → Low
Changed in hundredpapercuts:
status: Incomplete → Confirmed
Revision history for this message
Aaron Peachey (aaronp) wrote :

Note, this is the text of the private message that Nickserv sends to you after you've identified with your nick, even if you do so in any IRC app by manually messaging Nickserv (/msg nickserv identify password).
I believe the app is just passing NickServ's message through to the user, in which case NickServ's response message would need to be changed or telepathy-idle would have to catch the message, and replace the 'for' with 'as' before displaying it to the user.

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

Since this is a problem with the message NickServ send directly to the user, I am removing the task for telepathy-idle. Fixing this problem in code would be far more difficult than simply changing the text of the message NickServ send at the source, so I am attempting to track down the maintainer of the NickServ source code.

Changed in hundredpapercuts:
status: Confirmed → In Progress
Changed in telepathy-idle (Ubuntu):
status: Confirmed → Invalid
Changed in telepathy-idle (Ubuntu):
assignee: nobody → Chris Wilson (notgary)
Changed in hundredpapercuts:
importance: Undecided → Low
Changed in telepathy-idle (Ubuntu):
assignee: Chris Wilson (notgary) → nobody
affects: telepathy-idle (Ubuntu) → ubuntu
Changed in ubuntu:
assignee: nobody → Chris Wilson (notgary)
assignee: Chris Wilson (notgary) → nobody
affects: ubuntu → telepathy-idle (Ubuntu)
Changed in telepathy-idle (Ubuntu):
assignee: nobody → Chris Wilson (notgary)
assignee: Chris Wilson (notgary) → nobody
Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

Unassigning myself. I don't have time to work on this.

Changed in hundredpapercuts:
status: In Progress → Triaged
assignee: Chris Wilson (notgary) → nobody
Revision history for this message
Vish (vish) wrote :

Chris, the telepathy-idle (Ubuntu) task has been closed and there is no nickserv package, where is this bug in ?

Changed in hundredpapercuts:
status: Triaged → Incomplete
Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

The bug isn't in an Ubuntu package, rather it is the result of a badly constructed message sent from the Freenode nickserv.

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

I'm not sure how the IRC bots are developed and maintained, if it's only a problem with Freenode's particular implementation, or if this would be a problem on any IRC network.

Revision history for this message
Brian Curtis (bcurtiswx) wrote :

Yes, this is a Freenode bot response. Nothing we can do with it. Sorry.

Revision history for this message
Vish (vish) wrote :

Closing task as per comment #11

Changed in hundredpapercuts:
status: Incomplete → Invalid
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.