Description of problem: During normal operation the desktop will pause for several seconds, when this happens windows cannot be selected (either by mouse or alt tab), activities can't be toggled (if in activities can't get out, if on desktop can't get activities). Nothing accepts keyboard input. This state lasts a variable amount of time, it seems to be connected to having activities running in the background, but does not always happen (for instance I can run hugin compositing in the background without experiencing this). It is very frustrating when it occurs as there's no way to see what the system is doing or how long it might last. Occassionally the mouse cursor will also be frozen. Not sure if this is linked to the pause when bringing up the applications menu in activities (several seconds) or if that requires a separate bugzilla entry. Version-Release number of selected component (if applicable): Most recent gnome shell from updates (gnome-shell-3.0.2-4.fc15? Not at the machine currently) How reproducible: Intermittent. Additional info: Happens on two systems: Vaio C2M/W with intel 950GMA graphics, T5500 Core 2 duo, 1GB RAM AMD Athlon IIX4 640 (quad core), 512MB Geforce 9400GT, 1.5GB RAM Both running 64 bit F15.
Confirming version: gnome-shell-3.0.2-4.fc15.x86_64.
I also see this on a Lenovo T61 laptop. The entire user interface appears to freeze for varying durations, anywhere from several seconds to upwards of several minutes. A typical duration is 20-30 seconds. I have on several occasions had to wait 2-3 minutes. Not entirely sure how gnome-shell is organized but what I'm seeing appears to be as if the "window manager" has stopped responding. gnome-shell-3.0.2-4.fc15.i686
This has started occurring to me as well, after upgrading to Fedora 16. This is running on a Dell Precision M4400 laptop, with a nVidia Corporation G96 [Quadro FX 1700M] video card, running the nouveau driver. gnome-shell-3.2.1-2.fc16.x86_64
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Please can someone change this to F16 or rawhide, as this still occurs for me on F16 and I see no reason to think it's been addressed? Probably also "needinfo" should be applied as it's a nasty intermittent bug.
Created attachment 619534 [details] dmesg
Created attachment 619535 [details] Xorg.0.log
Created attachment 619536 [details] .xsession-errors
Created attachment 619537 [details] .xsession-errors-old
Created attachment 619538 [details] var log messages attached: dmesg, Xorg.0.log, .xsession-errors, .xsession-errors-old, /var/log/messages from approximate time of one of freezes (delayed response to mouse/keyboard_inputs/program_responses). still having intermitant display freezes but not sure what to relate it in logs, (if only xsession-errors had a timestamp lol.) currently running: kernel-3.5.4-2.fc17.x86_64 xorg-x11-drv-ati-6.14.4-6.20120602git930760942.fc17.x86_64 control-center-1:3.4.2-1.fc17.x86_64 gnome-settings-daemon-3.4.2-3.fc17.x86_64 dconf-0.12.1-1.fc17.x86_64 gconf2-3.2.5-2.fc17.x86_64
I have started to experience the gnome-shell since doing a re-install to Fedora 18 x86_64 from Fedora 16 x86_64. In my cause, the gnome-shell pauses for 10 seconds each time. It only happens when clicking on activities or pressing the windows key (keyboard shortcut).
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.