Grondr, thank you for your in-depth and exhaustive analysis. It will prove to be very valuable. I have marked this report as "Confirmed" for metacity, and I hope that will help capture the attention of the metacity maintainers.
I think you have a much better handle on what is going on than I do, and doubt I would be able to do a proper summary of the issue. If you are willing, could you please update the description above with a summary of: symptoms, diagnosis/causes, and possible work-arounds. Usually, when I revise a description, I set those things as subsections with headers like so:
=== Symptoms ===
.......
=== Diagnosis ===
....
=== Work-arounds ===
....
Bug reports that are nicely formatted like this are more likely to be dealt with by maintainers. I hope this helps get their attention and that they then can resolve this issue for you.
Grondr, thank you for your in-depth and exhaustive analysis. It will prove to be very valuable. I have marked this report as "Confirmed" for metacity, and I hope that will help capture the attention of the metacity maintainers.
I think you have a much better handle on what is going on than I do, and doubt I would be able to do a proper summary of the issue. If you are willing, could you please update the description above with a summary of: symptoms, diagnosis/causes, and possible work-arounds. Usually, when I revise a description, I set those things as subsections with headers like so:
=== Symptoms ===
.......
=== Diagnosis ===
....
=== Work-arounds ===
....
Bug reports that are nicely formatted like this are more likely to be dealt with by maintainers. I hope this helps get their attention and that they then can resolve this issue for you.