Description of problem: Stop responding after entering one letter in the search field Version-Release number of selected component (if applicable): gnome-shell-3.2.1-2.fc16.x86_64. How reproducible: almost 100% Steps to Reproduce: 1. Press Alt+F1 / Windows key (and so on) in order to get search field ("Type to search...") 2. Type in search field one letter (I tried it with "g" and "r") Actual results: gnome-shell stops responding taking 100% of CPU. kill -15 doesn't help. I was able to kill it only with kill -9 Expected results: Display results of typed search. Additional info:
I can reproduce this problem exactly on f16.
Are you by any chance using a non-default theme? I noticed that this problem goes away if I switch back to the default theme. This was reported on this bug here: bug #754297.
*** Bug 754297 has been marked as a duplicate of this bug. ***
Same for me. Upgraded a Dell Insp 1420 from F15 to F16. This bug did not show up on my other machine (Dell Optiplex 755). Here are the differences in behavior: Upgraded the laptop first. It was choking on the desktop because caribou.x686 was installed (rather than the x86_64 version). Somehow, the machine figured out (after multiple Oops! crashes) that it should go to fallback mode, which worked. I corrected the caribou lib issue (yum remove caribou.x686 && yum install caribou), but wonder what other serious oversights are lurking. I describe that because the next machine (Opti 755) I upgraded never went thought the multiple failures and journey through fallback mode. And the Mod4-search works perfectly well. This is unfortunate. The paneled window view (after pressing the Mod4 button) and the search function are the main reason to love G3. P.S. If you hear my voice, keyboard shortcuts for the post-Mod4 paneled view are sorely needed. Tab between Windows|Activities|<what's next> and arrow keys (& hjkl) to move focus among windows. Thanks
(In reply to comment #4) > Same for me. Upgraded a Dell Insp 1420 from F15 to F16. > If you switch back to the default theme, does the freeze go away? It does for me.
Sorry if this displays a lack of knowledge... Haven't played with themes at all, but here is what I see: The following files are zero-length ~/.gconf/desktop/%gconf.xml ~/.gconf/desktop/gnome/%gconf.xml ~/.gconf/desktop/gnome/shell/%gconf.xml ~/.gconf/desktop/gnome/shell/windows/%gconf.xml sets the theme to Adwaita and button_layout (done via gnome-tweak-tool) The machine that has no problems also had a similar setup, without the theme setting. So, I removed the theme's entry element on the bad machine, logged out/in and tried again. Crash. Fired up Evolution to complaints that the gconf daemon had been shut down. Reboot to restart the daemon... In the gnome-tweak-tool's Theme tab, everything shows XXX(default) with one exception: Shell theme, which has a warning-ish yellow icon to the left and is blank. However, both machines show the same icon, so I doubt this reflects any meaningful problem. Can't find anything of note, in my .gconf dir or in /etc/gconf Am I missing the theme config that you're talking about?
Hi, I'm using Atolm theme. After installing today an update (gnome-shell-theme-atolm-3.2-1) - the issue was resolved.
I confirm that Atolm works for me too. Gaia still crashes it.
BTW, atolm did crash me with this bug until it was updated.
A bit more info I crashed it a few times more and watched carefully. The crash happens in two stages: 1. Mod4, 'a' The desktop blanks for a second, then redraws itself from a the background image. At this point, everything behaves normally. But, sometimes another window pops up in the lower right corner of the desktop. It looks just like the search text entry window that pops up in the lower right corner of Nautilus after you type C-f. It accepts the rest of the search string, but to no avail, as the gnome desktop back up. 2. After the redraw - Mod4, 'a' The 'Oh no!...' crash screen comes up. I thought I saw that search text entry window once, but can't seem to reproduce it. Other notes: - I use the dvorak keyboard layout. Could that be an issue? - I mentioned a gconf daemon crash. More precisely: Evolution couldn't call up gconfd on the d-bus. This actually only happened twice (both in the same login session). I can't seem to reproduce this one. I started monitoring gconfd-2 and gconf-helper though the test crashes, and never saw either PID change at all. The gconf daemon crash may be a pink herring.
Created attachment 565873 [details] Gnome Shell crashes when searching a program from activities. I opened a new profile and escaped from bad configurations. However, still sometimes gnome shell kills itself when I search something from activities.
(In reply to comment #2) > Are you by any chance using a non-default theme? I noticed that this problem > goes away if I switch back to the default theme. This was reported on this bug > here: bug #754297. I did some changes with tweak tool.
.xsession-errors (gnome-shell:22512): folks-DEBUG: individual-aggregator.vala:305: Setting primary store IDs to defaults. (gnome-shell:22512): folks-DEBUG: individual-aggregator.vala:333: Primary store IDs are 'eds' and 'system'. (gnome-shell:22512): Clutter-WARNING **: Attempting to add actor of type 'ShellGenericContainer' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'. (gnome-shell:22512): St-WARNING **: Actor of type 'ShellGenericContainer' is not a child of the StBoxLayout container JS ERROR: !!! WARNING: 'assignment to undeclared variable removeTopBar' JS ERROR: !!! WARNING: file '/usr/share/gnome-shell/extensions/icon-manager/extension.js' line 88 exception 0 number 156 JS ERROR: !!! WARNING: 'assignment to undeclared variable iconManager' JS ERROR: !!! WARNING: file '/usr/share/gnome-shell/extensions/icon-manager/extension.js' line 94 exception 0 number 156 JS LOG: GNOME Shell started at Sat Mar 10 2012 22:58:09 GMT+0100 (CET) ** Message: applet now embedded in the notification area still crash....
still crashing on: GNOME Shell 3.2.2.1 Linux Kernel 3.2.10-3.fc16.x86_64
It works with NVIDIA driver 295.33 No more crashes here :D
I removed a nautilus-pastbin plugin and everything just worked. Thank the f'in lord. Add/Remove Software, search for nautilus-pastebin, uncheck, Apply
Yes, it works with NVIDIA's new driver! I updated it and now it's okay. Therefore, I think it's solved.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.