GNOME Bugzilla – Bug 646252
Replies in message tray don't show up in not-yet-opened Empathy chat window
Last modified: 2011-12-08 04:01:44 UTC
Using latest jhbuild of gnome-shell on Ubuntu 10.10 (Empathy 2.32.1, so not sure if Empathy trunk handles this better): When an IM arrives, the Empathy tray icon blinks, and the gnome-shell message tray shows the IM. If I use the message tray to respond, and then later open up the Empathy chat window by clicking on the blinking tray icon, the chat window only has the IMs that have arrived, and not the ones that I've sent. If the chat window is already opened, both message-tray and chat window display incoming and outgoing IMs, regardless of which one is used to send them. Somewhat related, the interaction between the chat windows and message tray seems kind of confusing on the whole... maybe i'm just having trouble wrapping my head around 2 views of the same thing, but a bunch of minor bugs make them not-quite-the-same? for example, i can read messages in the tray, but empathy doesn't think they've been read until the chat window is opened & receives focus. Also hard to tell which lines in the message tray are from me, and which are from the contact.
Reporting the same issue on Fedora 15 beta, Empathy 3.0.1, gnome-shell 3.0.1. I have a slight variation though, instead of not showing the outgoing messages at all I see the outgoing messages all grouped up above the incoming messages. It looks as if I had sent all of my messages in a row, then my contact sent all of their messages in a row.
I have the same issue (Choobie's version) using latest Jhbuild on Ubuntu 11.04.
"Choobie's version" is actually the same thing I was seeing in the original report; just didn't notice the greyed out messages above the incoming requests. Also seeing the same behavior on ubuntu 11.04 + gnome3 ppa, so not fixed in 3.x empathy.
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 648793 ***