Red Hat Bugzilla – Bug 149083
window list is BROKEN, groups too early, etc.
Last modified: 2007-11-30 17:11:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041228 Firefox/1.0 Fedora/1.0-8
Description of problem:
Due to recent menu upgrades (read breackages) I have had to change to the silly two panel format. I removed all my settings for panel and metacity.
Now, my windows are grouped if I have more than three open, I have played with default settings of 4096 max size to about 600. It doesn't change a thing.
Now when I click on a window in the window list, it isn't raised unless (and then only sometimes) there are no grouped windows. This used to work whether or not the windows were grouped.
* Windows don't automatically popup and take focus when they are new like they used to.
* Window titles, such as terminal (which is the main culprit in the previous issue bullet), often stay bold for some rediculous period of time.
* Windows seem to change order in the window list. This is bad, once there, they shouldn't change order... especially now that they are all on one line.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Please, see ultra thorough description above
Actual Results: Please, see ultra thorough description above
Okay, there's a lot of verbage here which makes it very difficult to
figure out what bug you're trying to describe, but I think its the
"clicking on grouped windows doesn't raise" bug.
*** This bug has been marked as a duplicate of 148915 ***
It is more than just it doesn't raise. The grouping happens WAY TOO
EARLY. You set the maximum width to 4096 (was the default), and yet
after three windows being opened, they grouped. Not only that, but the
window list compresses the buttons for them long before they need to
be compressed (shrunk, whatever).
This doesn't happen, I don't believe, with the single larger panel
(which I had been using until the recent forced change (Due to menu
As for the not raising, yes, that seems to be the one you marked this
as a duplicate of. However, it is not a duplicate of that, that was a
sub, possibly related, bug.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.