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 660705 - Superfluous, trivial name change notifications
Superfluous, trivial name change notifications
Status: RESOLVED DUPLICATE of bug 660774
Product: gnome-shell
Classification: Core
Component: telepathy
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Shell Telepathy maintainer(s)
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-02 17:16 UTC by benoit.hiller
Modified: 2011-10-12 14:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
example of two identical "known as" notifications (11.69 KB, image/png)
2011-10-02 17:16 UTC, benoit.hiller 		Details

Description benoit.hiller 2011-10-02 17:16:35 UTC 
Created attachment 198032 [details]
example of two identical "known as" notifications

Every time one of my messages is followed by a message from the other user, their message is prefixed by [Fullname] is now known as [Fullname]. It also occurs when there is a significant pause between the other user's messages. This is only when viewing the conversation as a notification bubble and occurs for both kinds of notification bubbles.

I have only tested this with "facebook" and "gmail" accounts so I do not know if it is just xmpp.

For replication purposes I am using the aforementioned version on arch linux with the corresponding version of gnome shell and libnotify 0.7.4-1.

Attached is a screenshot of this occurring in the tray style bubbles.
Comment 1 Guillaume Desmottes 2011-10-12 14:28:24 UTC 
Gnome-Shell issue.
Comment 2 Jasper St. Pierre (not reading bugmail) 2011-10-12 14:54:01 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 660774 ***