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 686880 - (First) notification from empathy doesn't contain any text
(First) notification from empathy doesn't contain any text
Status: RESOLVED NOTGNOME
Product: gnome-shell
Classification: Core
Component: telepathy
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Shell Telepathy maintainer(s)
gnome-shell-maint
: 685868 688303 689558 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-10-25 17:47 UTC by Žygimantas Beručka
Modified: 2012-12-05 12:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
js error backtrace (2.56 KB, text/x-log)
2012-10-25 21:42 UTC, darkxst
Details

Description Žygimantas Beručka 2012-10-25 17:47:59 UTC
I'm just copy&pasting the report by the original reporter from Launchpad (bug #1049210) since a lot of people are having this issue but no attention is being paid by Ubuntu devs.

---- cut ---

The problem occures with the combination of gnome-shell and empathy but I had to choose only one package...

When I receive a message from someone through empathy (connected to google talk) and the window for chatting with that person is not opened yet, the notification trai contains an icon for that person but the text content is missing and empathy's chat window doesn't open but if you open it manually the text is there.
After replying in gnome-shell notification window you get all the new messages that the person writes afterwards without any problems but you never get the old messages.

How to reproduce:
Open empathy chat window (google talk).
Say something to someone.
When that person replies write him something back in gnome-shell notification window and then close the empathy chat window on desktop (or if the window isn't opened yet just double click on gnome-shell notification window and close empathy window then after replying).
When that person replies back you will only get the notification icon without the text. Also the notification window won't pop up from notification tray and empathy chat window won't open.
If the person writes something else the notification window will pop up as normal containing the text that that person wrote next (without the text that was written first).

---- cut ----

This was reported for another version, but I'm having what seems to be the same bug (or at least a very similar one) on 3.6.1. There is no text shown on first notification, just an empty bubble. But once a person writes you another message, this second message (and the rest that follow) is shown in the chat notification bubble.
Comment 1 darkxst 2012-10-25 21:42:44 UTC
Created attachment 227310 [details]
js error backtrace

attaching backtrace of JS error from session.log, that occurs when the notification is received.
Comment 2 Jasper St. Pierre (not reading bugmail) 2012-10-25 21:48:30 UTC
This is a known issue, and we have no idea what's causing it.

There's a suspicion that:

http://cgit.freedesktop.org/telepathy/telepathy-logger/commit/?id=f5a91c2f48c60bc0b8fc53e915b66603bfff4dd3

this might fix it, but it doesn't make sense to me. Can you try applying that patch on a locally-built telepathy-logger and see if it fixes it?
Comment 3 darkxst 2012-10-25 23:41:35 UTC
Jasper, yes that patch fixes it.
Comment 4 Jasper St. Pierre (not reading bugmail) 2012-10-31 14:19:53 UTC
*** Bug 685868 has been marked as a duplicate of this bug. ***
Comment 5 Guillaume Desmottes 2012-11-01 07:49:22 UTC
telepathy-logger 0.6.0 has been released with this fix.
Comment 6 Guillaume Desmottes 2012-11-06 11:08:06 UTC
Closing this bug for now. Please re-open if you experience this bug with telepathy-logger 0.6.0.
Comment 7 Jasper St. Pierre (not reading bugmail) 2012-11-29 20:09:59 UTC
*** Bug 688303 has been marked as a duplicate of this bug. ***
Comment 8 Guillaume Desmottes 2012-12-05 12:03:39 UTC
*** Bug 689558 has been marked as a duplicate of this bug. ***