I have Gnome shell 3.2 and a gnome 3.2 theme installed. But when I use the search bar in Activities, gnome shell freezes and I am left with no other option except to restart the system. Is this a bug? Or is there any solution for this?
|
closed as off topic by jrg♦ May 22 '12 at 18:42
Questions on Ask Ubuntu are expected to relate to Ubuntu within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.
|
I know this isn't a fix (I too have issues with the shell freezing, but not on the search iteself), but you can do the following to restart the shell: Alt+F2, type 'r' and press return. Even if the alt+f2 dialog doesn't show, it will still take your command and run it. This restarts the shell but doesn't log you out or anything. |
|||||||||
|
|
this is happening to me and i dont have a solution to prevent it but here is a way to get out of it without restarting gdm:
This allows you to save any work. and not lose any windows when the lockup occurs. Its possible to combine the ps and kill into one elegant command. Someone else can do that....I'm looking for a solution to the search issue. MORE INFO: This happens to me 100% when I search. The solution I found was to change the shell theme to default Ubuntu GNOME 3 using the gnome-tweak-tool. This fixed me up. Seems like certain themes have compatibility issues. |
||||
|
|
|
There is probably not an easy solution, you would have to file a bug report upstream with gnome for any type of resolution. FWIW I filed a similar bug report with gnome a few months ago now (was using Fedora 15 at the time). In my experience :
I also had lockups when using the search, often I could recover by restarting gnome-shell (Alt + F2 , hit the r then Enter - you may not see any output on the screen during that sequence of keyboard activity ), or restarting X (did not have to hard boot with a lock up when searching). When this (lockups) happens, you will need to ssh in from another box and pull the logs (for bug reports). FWIW, here is an example of the kind of information you will be asked (probably from upstream) https://bugzilla.redhat.com/show_bug.cgi?id=716619 I know it is old and from fedora, but, that is the sort of thing you are looking at and I can tell you from personal experience what the gnome developers will expect. FWIW, the bug report I filed with gnome.bugzilla was unresolved and is so old that it no longer exists (I searched). At the end of the day, it was easier to upgrade the nvidia card. |
|||
|
|
|
revert the theme into the original theme or download theme that is compatible with gnome shell version that you have. |
|||||
|
|
To recover, probably a cleaner way is to terminal via ctrl+alt+f1 and then restart lightdm.
|
|||
|
|
|
this is a known problem. you can temporarily remove nautilus-pastebin plugin, until the upstream patch makes it into Ubuntu. for more details, see the upstream bug. |
|||
|
|
|
may be this can help you.. |
|||||
|