Red Hat Bugzilla – Bug 134625
Gnome extremely slow after aplication crash
Last modified: 2007-11-30 17:10:50 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041002 Firefox/0.10.1 Description of problem: First: I don't know if that is really connected with metacity or maybe nautilus or libgnome or other!!! Some apps crashes. That's normal. But when I end one with "Appp not responding > Close" dialog the Gnome slowes. Mouse, kbd, menus work normal it is fast. But when I want to rune new app or open new window of running app I have to wait more tha 10 seconds to see the window. In between the other windows are somewhat frozen. The problem does not appear in KDE. Solution is to restart X (CTRL+SHIFT+BACKSPACE). But after that the Gnome often fails to load (this is another bug as I think). So I have to go to runlevel 3 and then runlevel 5. In the console, when I type "init 3" I have to switch to another console and back to first to be able type new command "init 5" (and this is also another bug). Version-Release number of selected component (if applicable): metacity-2.8.5-1 How reproducible: Always Steps to Reproduce: 1.Close not responding App in gnome 2.Try to run new app, e.g. gedit 3. Actual Results: Waiting more than 10 second to see new window opened Expected Results: New window opened quickly Additional info: Toshiba Satellite 1135-S1554 (mobile pentium 4 2.2 GHz, 512 RAM, Intel 85x gfx card, etc.) I do upgrades everyday. I've been testing FC3test2 since it release.
The problem is still here after upgrades form 07.10.2004 libgnome-2.8.0-1 metacity-2.8.5-1 kernel-2.6.8-1.541 So the only usable desktop environment at the time is KDE, what AFAIK is not the default desktop for Fedora.
Hi, after everyday upgrade form rawhide (today is 15.10.2004 it is four days after FC3TC release) the problem still exists but in rather slightly form. Now the problem shows after error in SMB browsing error in Nautilus. After such error there shows quite big delays in such operations as: -opening new window -entering to MenuStart on Panel the problem does not generate significant CPU load and vanishes after about a minute. After that Gnome works as it should. Can somebody confirm this bug?
Half day before FC3 final release and the problem persists :(
I haven't seen this problem or heard of other people having it; how do you reproduce? Which apps are not responding?
Many apps presents same behavor. For example. Start Gnome app (it can be system-config-display, gthumb, tux-commander or other). Just work with it for a while. In roandom time the app stops reponding immediately. It responds but after rather long time (up to minute). Responding I mean e.g. opening new window from within the app, entering Start Menu or running other app (e.g. firefox from launcher placed on gnome-panel). Everything work, but slow. There is amost no CPU load, just normal CPU load (few %). It seems like waiting for some timeouts. This problem (slowness) can be initiated by various gnome apps, but for example not with Firefox which is (AFAIK) non gnome app.
Can you think of anything unusual about your system? What kinds of things have you installed/configured?
Any non-default window manager settings? Does changing them back to defaults help?
Yes, I've changed many properties. Among athers it was screen DPI (which involves other problem with displaying pages in Firefox) and Font Sizes. I cannot revert as I just did clean install of FC3 isos. I left untouched my /home partitions but deleted most of config files (.gnome2 and others in my ~ dir) before first gnome start. After gnome start I lost antialias on all fonts except fonts in gnome-terminal. Changing fonts setting cannot fix it. I had to create nue user, move important data to new acconut. New user has antialiased fonts always (but I don't touch the settings now:). The problem of gnome slowness does not appear in FC3 at all.
You're saying that the problem disappeared with a clean install of FC3, but was in FC3test2, right? Hmm. I don't have any ideas.
Yes it did. But today I've seen it again :(
Hi Bednar, Are you still seeing this problem?
No response from reporter for six months to info request. Closing.