Maximized windows disappear
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maximus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 9.04 Jaunty Netbook Remix daily (as of today april, 22 2009)
Hardware: eeeBox b206
Not using compiz, but tried to enable it, then I disabled it, I don't know if this all started because of this tryout... before that I managed to use the freshly installed distro for about 30minute without hiccups.
Whenever I click on an application that can be maximized (click performed using the netbook-launcher), I can se it's automatically maximized, but, just after that, the window and the upper panel both disappear, I can see a faded netbook-launcher, I cannot click on anything on the netbook-launcher, but it seems the maximized window is focused since I noted I can click on it (even without seeing it), i.e. if the window is a terminal, I can write in it even if I can't see it...
If I click on the area where normally the go-home applet is located, the netbook-launcher, and the panel, both reappear at full opacity, If i click on the maximized application (using the window switcher applet next to the go-home one), the app won't appear and, again, the netbook-launcher fades to almost 40%, and the panel disappears) and the application gains focus (but still remains transparent) again.
If I click on the go-home (to see the application icon) button, the right click on the application button and select Demaximize on the context menu, then I can see the demaximized aapplication window (it appears above the netbook-launcher where it would have been in the maximized shape).
If in gconf-editor I disable the auto maximize option in maximus, I can always see the applications window (demaximized, of course), if I maximize it again, the window disappears again.
Changed in maximus (Ubuntu): | |
status: | Incomplete → New |
Thanks for reporting this bug. Could you please check to see if the /apps/metacity/ general/ compositing_ manager gconf key is set to false. Also, can you confirm that windows don't have shadows. The behaviour you describe seems to indicate a compositing manager is running, which the default Intel drivers don't support (compositing + launcher don't work together in Intel graphics).