Bug 754297

Summary: Any gnome-shell theme other than default causes search to lock up GUI
Product: [Fedora] Fedora Reporter: Hugh Caley <hughc>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: alex, browning48ky, maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-19 01:11:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Hugh Caley 2011-11-16 01:19:07 UTC 
Description of problem:
When running any of the available gnome-shell themes other than Default, if I type anything into the search window the GUI locks up.  I have to kill the X session or kill the gnome-shell process in a console to escape.

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1.Change gnome-shell them using gnome-tweak-tool to anything other than default
2.click on "Activities"
3.type a few letters
  
Actual results:
GU locks up (except for mouse movement).  If I switch to a pseudo tty and check top the gnome-shell process is now taking 100% of cpu and will continue to do so until I kill it.

Expected results:
performs the search

Additional info:
I've tested with both the Nouveau and proprietary nvidia drivers (using Nvidia Geforce 210 video).  Dual display, with both video drivers (twinview using Nvidia drivers).  I've tried it with the shell themes Atomlm, Dark Glass, Gaia, and Orta.  No errors in /var/log/messages, Xorg.0.log or dmesg.
Comment 1 Alex Lancaster 2011-11-19 00:04:47 UTC 
I have the same problem.  It looks like this may be the same problem as bug #752704, because if I switch back to the default the problem goes away.
Comment 2 Hugh Caley 2011-11-19 01:11:57 UTC 

*** This bug has been marked as a duplicate of bug 752704 ***