window placement problems with compiz

[Rafał Próchniak]

Binary package hint: compiz

Gutsy (updated as of February 7th, 2008), compiz from Ubuntu repositories
Relevant (I hope) compiz settings:
Workarounds on: all but Legacy Fullscreen Support (disabled or otherwise F-Spot doesn't work in fullscreen)
Windows Placement: different, doesn't matter (checked different settings: with or without workarounds, smart or not)

Problems concern mostly maximized windows. Metacity behaves as expected (maximized windows are remembered as maximized):

1. Windows (for example OpenOffice.org, F-Spot) closed while maximized are not maximized and they extend to the next viewport to the right (several pixels, but they are recognized as present on this other viewport). Enabling "Legacy Fullscreen Support" fixes this issue.

2. PDF documents (in evince) first open maximized to blink after fraction of a second and reduce in size to more less quarter screen size. With "centered" placement some documents open in maximized size but with top left corner centered (with half window offscreen). Disabling Workarounds doesn't help.

Is there anything I could add to this report?

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. I tried recreating this bug report using Hardy Heron and was unsuccessful. You might also be interested to know that in Hardy F-Spot works in fullscreen with Legacy Fullscreen Support. It would be helpful if you could either test this with Hardy yourself using an Alpha LiveCD - it should be recreatable without installing. You can learn more about Hardy Heron at http://www.ubuntu.com/testing . Alternatively, if you were to backup your compiz settings using CompizConfig Settings Manager and as them as attachment to your bug report that would be helpful too. Thanks in advance.

[Rafał Próchniak (burlap)]

Before I finally manage to get nvidia driver working under LiveCD (nvidia-glx-new seems to require a new kernel, which is, I guess, not possible under LiveCD, next time I'll try to compile or use nvidia binary, it is difficult as I have to do it offline - alpha 4 already crashed twice - probably due to ralink problems), I've attached my compiz config file.

[Rafał Próchniak (burlap)]

I finally tested with Hardy Alpha 4 (with nvidia drivers from nvidia website installed in LiveCD).

F-spot working in fullscreen with legacy support solves #1.

#2 persists - after desktop effects are enabled, evince doesn't remember window size settings and resizes itself. Perhaps it's an evince bug?

[Travis Watkins (amaranth)]

Indeed, evince is asking to be positioned a certain way twice. However, can you see if disabling "workaround" in the Window Placement plugin fixes this? Install compizconfig-settings-manager and go to System->Preferences->Advanced Desktop Effects Settings.

[Rafał Próchniak (burlap)]

Disabling workarounds doesn't help in Gutsy, I'll try to test Hardy this week.

[Rafał Próchniak (burlap)]

It's the same in Hardy final. And also, there is this bug (on evince): https://bugs.launchpad.net/ubuntu/+source/evince/+bug/198192

[Hew (hew)]

I can confirm this issue on Hardy release. The window needs to have been previously maximised on close. When a new pdf is opened, it says "Loading" in the maximised state for an instant, then flicks to the windowed state in the top left quarter of the screen. I tried disabling every option in ccsm, but the issue still occurs.

[Rafał Próchniak (burlap)]

Just one more remark - the evince problem persists whether workarounds are turned on or not, while I'd prefer to keep them on - this is the only way to make nautilus spatial mode work correctly under compiz...

[Danny Baumann (dannybaumann)]

The "evince opens maximized, then resizes itself" issue as well as the "spatial nautilus windows move down/right on every reopen" are fixed in Gtk 2.12.10...don't know when/if that will land in Hardy, though.

[Sebastien Bacher (seb128)]

is that still an issue in intrepid using the new gtk?

[Robert Ancell (robert-ancell)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!