From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4 Description of problem: I have been using a gnome-panel with just the window list applet and the expand property set. This means that the panel expands every time i open a new window. However, I often get a problem when the panel is close to filling the width of the screen and I open a new window. This causes the panel to resize to the full width of the screen and then to a more compressed range, then back to full width again repeatedly until I open more windows, or close existing ones. This resulting in my CPU usage rocketing making the system sluggish very quickly. e.g. opening a window causing this problem will take several seconds before a prompt becomes available. This does not happen all the time, so it seems to depend on what the size of the panel is before the new window is added. However, if it does happen, then i close a window (e.g. a gnome-term) then start it back up, the problem disappears and reappears. Version-Release number of selected component (if applicable): gnome-panel-2.8.1-3 How reproducible: Sometimes Steps to Reproduce: 1. Create a gnome-panel with expand set and only the window list applet (I opened it across the top) 2. Open several windows until the panel is the width of the screen 3. panel cannot determine what size to be Actual Results: The panel switches from being fully expanded to compressed very quickly using a large amount of CPU to do so. Expected Results: The panel should choose one size to be and stick with it. Additional info: This is an issue I have had intermittently since I first created a separate gnome-panel. approx 6 months+ ago
Created attachment 115155 [details] View of panel A view of the panel when its resizing
Created attachment 115156 [details] Second view of panel Another view of the panel resizing
Do you still see the problem with FC4? I can't reproduce here ..
I have upgraded to fc4 and been running it for a week or so now. I have not encountered the problem so far and so would appear to be fixed. It seemed to happen quite regularly in fc3.