new upstream patch:

http://git.gnome.org/browse/gnome-shell/commit/?id=b121c2518403bc5ea991b3f1c4b00188c8d590b4

*** Bug 887298 has been marked as a duplicate of this bug. ***

I experience this problem since upgrading to Fedora 18. It occurs when using Empathy and its integration into Shell. Very annoying.

I encounter this frequently. It's very annoying.

i am experiencing this with gnome-shell-3.6.2-6.fc18.x86_64.  is this a gnome problem?  should we be logging this error with them?

(In reply to comment #5)
> is this a gnome problem?

Yes. The most relevant upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=683986, but unfortunately nobody managed to actually trace down the issue, though the pile of patches in that bug appears to have fixed the issue in 3.7.x.
I'd be willing to roll another 3.6.x release containing those patches if someone can step up and help with testing (we are approaching the end of the 3.8 cycle upstream, so not the best time for testing old stable for me :-)

i did log a bug with gnome too on this issue. i believe it to be in their court since my googling found it to occur on ubuntu as well. at this point, i'm willing to wait for a 3.7 release to install (if that's possible). this bug has inspired me to revisit a fluxbox wm just in case gnome drags their feet on a permanent fix. i need stuff working for work.

let me clarify:  the 3.7/3.8 cycle will mean waiting for the next full release of gnome before a fix can be achieved?  if that's the case, the i take back my previous reply to wait. i am willing to test out a shell fix for 3.6.x if you have the time to drop out a change.

this is just getting aggravating.

I would test it too. It would be great to have this fixed.

I'm also willing to test it.

by the way, for those suffering from this, a small workaround would be an in session restart of the gnome-shell by alt+f2 and typing "r" to restart the shell.  it's a built-in gnome put in, and it does restore the notification bar.  sucks to have to do this, but....

OK, I'll backport the patches and provide a build for testing. I'd like to wait for https://bugzilla.gnome.org/show_bug.cgi?id=689106 for another stable upstream release though.

sounds good.  thanks!

Ladies and gentlemen, here's a scratch build for your testing pleasures:
http://koji.fedoraproject.org/koji/taskinfo?taskID=4938856
(it contains all unreleased commits of the gnome-3-6 branch + the patch set attached to the aforementioned upstream bug)

i have applied the patch and will commence testing.  thanks again for the effort.

I am using 3.6.2-90.fc18.x86_64 and just experience a gnome-shell lockup. I was bringing put the activities overview and partway through the animation, it locked up and became unresponsive.

I was able to switch to a text console (ctrl+alt+f2) and kill gnome-shell. It restarted automatically and is working fine again.

This happened after about 2.5 hours of use on the new version.

I didn't have time to try to diagnose what happened. It may not have been related to the patches we are testing.

i have been using the gnome-shell-3.6.2-90.fc18.x86_64 patch, and things have been great.  i have not experienced the freeze that patrick states above, but i have been running the patch for well over 8 hours during work without any freezes and with a persistent message tray.  i use empathy actively during the day too.

thanks, florian, for the patch.  i'm giving it a pass on my end.

gnome-shell-3.6.3-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/gnome-shell-3.6.3-1.fc18

I've been using it for two days and this bug seems to be fixed. But I saw another one (probably caused by the patches).

When I plug in USB stick the notification moves down under the edge of screen. Only thing I can see is small part of 'x'.

It isn't so bad. You can click 'x' and everything is back again.

I made a screencast of this. You can find it here: http://pschindl.fedorapeople.org/Screencast.webm

(In reply to comment #19)
> I've been using it for two days and this bug seems to be fixed. But I saw
> another one (probably caused by the patches).

Yes, this is indeed a regression from one of the patches - see https://bugzilla.gnome.org/show_bug.cgi?id=689295 for the upstream issue. A build which includes the patch is on its way, I'll push an update later.

*** Bug 909988 has been marked as a duplicate of this bug. ***

I have not seen the message tray disappear since applying the patch, kudos and many thanks!

I did experience another lockup. This time I grabbed a core file with gcore and it appears I am experiencing bug 878323.

Even with the build from comment #14, I had the message tray disappear..

The only potentially relevant JS trace I could find are a bunch of:

Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
    JS ERROR: !!!   Exception was: TypeError: this._titleLabel.clutter_text is null
    JS ERROR: !!!     message = '"this._titleLabel.clutter_text is null"'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/messageTray.js"'
    JS ERROR: !!!     lineNumber = '462'
    JS ERROR: !!!     stack = '"("Username removed for privacy",null,[object Object])@/usr/share/gnome-shell/js/ui/messageTray.js:462
wrapper("ticklegrapes416.it",null,[object Object])@/usr/share/gjs-1.0/lang.js:204
([object _private_TelepathyGLib_Contact],1,"offline","")@/usr/share/gnome-shell/js/ui/components/telepathyClient.js:738
wrapper([object _private_TelepathyGLib_Contact],1,"offline","")@/usr/share/gjs-1.0/lang.js:204
"'

I believe this is fixed.

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.