| 2007-03-04 20:24:07 |
Profusion |
bug |
|
|
added bug |
| 2007-03-05 18:25:52 |
Brian Murray |
None: statusexplanation |
|
|
|
| 2007-03-05 22:32:56 |
Freddy Martinez |
firefox: status |
Unconfirmed |
Needs Info |
|
| 2007-03-05 22:32:56 |
Freddy Martinez |
firefox: assignee |
|
freddymartinez9 |
|
| 2007-03-05 22:32:56 |
Freddy Martinez |
firefox: statusexplanation |
|
Is this in Feisty? |
|
| 2007-03-06 00:52:32 |
Freddy Martinez |
None: assignee |
freddymartinez9 |
|
|
| 2007-03-06 00:52:32 |
Freddy Martinez |
None: statusexplanation |
Is this in Feisty? |
|
|
| 2007-03-17 18:08:48 |
Arthur Peters |
title |
Cannot see firefox window invisible when maximized when desktop effects is enable. |
Invisible windows when desktop effects is enabled |
|
| 2007-03-17 18:21:03 |
Arthur Peters |
compiz: status |
Needs Info |
Confirmed |
|
| 2007-03-17 18:21:03 |
Arthur Peters |
compiz: statusexplanation |
|
I can confirm that is problem exists on current Feisty (as of 2007 03 17). I am using a Compaq Presario R3000z with a NVidia Geforce 440 Go using the nvidia proprietary driver.
However I cannot predictable reproduce it using the method in the original report. It seems to be related to the window being maximized, especially if the program starts maximized (like firefox often does, because of common usage). It has happened to me on multiple different programs (gedit, firefox, gconf-editor, rhythmbox), so it is not specific to firefox. It seems like it might be a non-deterministic button like a timing bug (threading).
Can anyone give any guidance on how to produce useful debug output from compiz to try to diagnose this bug?
For the record, when I used compiz (and beryl) 3-4 months ago I never say this problem, so I don't think this is a fundamental problem in the software or a hardware incompatibility.
-Arthur |
|
| 2007-03-21 08:57:30 |
Mark Reitblatt |
compiz: importance |
Undecided |
High |
|
| 2007-03-21 08:57:30 |
Mark Reitblatt |
compiz: statusexplanation |
I can confirm that is problem exists on current Feisty (as of 2007 03 17). I am using a Compaq Presario R3000z with a NVidia Geforce 440 Go using the nvidia proprietary driver.
However I cannot predictable reproduce it using the method in the original report. It seems to be related to the window being maximized, especially if the program starts maximized (like firefox often does, because of common usage). It has happened to me on multiple different programs (gedit, firefox, gconf-editor, rhythmbox), so it is not specific to firefox. It seems like it might be a non-deterministic button like a timing bug (threading).
Can anyone give any guidance on how to produce useful debug output from compiz to try to diagnose this bug?
For the record, when I used compiz (and beryl) 3-4 months ago I never say this problem, so I don't think this is a fundamental problem in the software or a hardware incompatibility.
-Arthur |
|
|
| 2007-03-24 14:25:05 |
Travis Watkins |
marked as duplicate |
|
89189 |
|
| 2007-03-24 14:25:25 |
Travis Watkins |
compiz: status |
Confirmed |
Rejected |
|
| 2007-03-24 14:25:25 |
Travis Watkins |
compiz: statusexplanation |
|
This seems to be bug 89189. |
|
