Description of problem: After 3-4 minutes gnome shell session becomes unusably slow, Xorg jumping up to 100% though having 4 cores doesn't really help Version-Release number of selected component (if applicable): $ rpm -qa | grep gnome-shell gnome-shell-extension-weather-0-0.2.git5c61d80.fc17.noarch gnome-shell-extension-drive-menu-3.4.0-1.fc17.noarch gnome-shell-3.4.1-5.fc17.x86_64 gnome-shell-extension-gpaste-2.8.1-1.fc17.noarch gnome-shell-extension-icon-manager-0-0.6.git37fbd9a.fc17.noarch gnome-shell-extension-common-3.4.0-1.fc17.noarch gnome-shell-extension-alternative-status-menu-3.4.0-1.fc17.noarch gnome-shell-extension-righthotcorner-1.0-2.fc17.noarch gnome-shell-extension-native-window-placement-3.4.0-1.fc17.noarch gnome-shell-extension-remove-accessibility-icon-20111008-3.fc17.noarch gnome-shell-extension-calc-0-0.3.git2fca097.fc17.noarch gnome-shell-extension-noim-1.0-2.fc17.noarch gnome-shell-extension-presentation-mode-0-0.3.gitc3ce6b2.fc17.noarch gnome-shell-extension-iok-0.20120423-2.fc17.noarch gnome-shell-extension-cpu-temperature-0-0.7.gite1777e6.fc17.noarch gnome-shell-extension-xrandr-indicator-3.4.0-1.fc17.noarch gnome-shell-extension-remove-volume-icon-0.4.0-1.fc17.noarch gnome-shell-extension-workspace-indicator-3.4.0-1.fc17.noarch gnome-shell-extension-pidgin-0-0.7.git87fc23433d.fc17.x86_64 gnome-shell-extension-theme-selector-0.9-4.fc17.noarch gnome-shell-extension-alternate-tab-3.4.0-1.fc17.noarch gnome-shell-extension-auto-move-windows-3.4.0-1.fc17.noarch gnome-shell-extension-windowsNavigator-3.4.0-1.fc17.noarch gnome-shell-extension-apps-menu-3.4.0-1.fc17.noarch gnome-shell-extension-workspacesmenu-0-2.fc17.noarch gnome-shell-extension-mediaplayers-0-0.3.git1225d49.fc17.noarch gnome-shell-extension-dock-3.4.0-1.fc17.noarch gnome-shell-extension-user-theme-3.4.0-1.fc17.noarch gnome-shell-extension-places-menu-3.4.0-1.fc17.noarch gnome-shell-extension-systemMonitor-3.4.0-1.fc17.noarch gnome-shell-extension-pomodoro-0-0.3.git13030cd.fc17.noarch gnome-shell-extension-noripple-2.0-1.fc17.noarch gnome-shell-extension-remove-bluetooth-icon-0.3.0-1.fc17.noarch note not all extensions are enabled How reproducible: happens in both Gnome-shell and Cinnamon Steps to Reproduce: 1. Start a new session, open usual email, firefox, eclipse 2. do something for 4-5 minutes Actual results: session become very slow untill standstill, ctrl+alt+backspace works though Expected results: no performance issues! Additional info: I use nouveau drivers. There are no performance issues when using MATE desktop with compiz enabled.
Created attachment 593958 [details] Xorg over 80% CPU...
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.