Bottom part of maximized windows missing sometimes

Hi Shane,

Thanks for reporting this. This is a known issue with Shotwell and has been ticketed upstream: http://redmine.yorba.org/issues/4966

If you'd like to follow the progress of this bug upstream, please create a Yorba Redmine account and follow the issue linked above.

Thanks!

I have seen this problem for gitg & gitk as well.

I've seen this issue in both Shotwell and Xiphos, two programs from two independent development teams. This makes me suspect the issue is actually with Unity Window Manager.

And the fact it only happens in unity 3D and not 2D would suggest the same.
It is quite disappointing to still see this issue in the default photo app 2 months after release.

I don't think this bug is specific to shotwell only. please see bug 993204 which shows it to be a problem with other apps as well.

I hope there will be a solution for every maximized window soon, I've this problem frequently!

If you toggle the app from maximized to not maximized and back, the bottom is fine. This only happens when you open apps maximized.

Chromium seems to be also affected by this bug, which is especially annoying, since the web browser is commonly most used application nowadays.

I was sure we fixed this recently, and that this bug must be a duplicate. Can anyone find the old bug?

I am unable to reproduce this bug anymore. Maximized Shotwell starts fine. Nothing is missing.

@all affected:

Can anyone still reproduce this bug in Compiz 0.9.10-dev/trunk ?

I'm no longer using ubuntu (and so not shotwell either) but I gave ubuntu 13.04 a test run and the shotwell window seems to be behaving as it should with no missing parts.

I still have this bug. Unfortunaletly, in a commercial software that you cannot download without buying...
But at least I confirm this is not solved, and still very annoying.

By the way, I have a fresh 13.04.
If I can make some further tests, feel ffre to ask me.

New information: this is not only happening with maximized windows, but also sometimes on small pop-ups (like dialog boxes or warnings). The problem is one cannot click on buttons unless the window can be resized.

In my case, it is likely to be related to the java version. Actually, the software I used is still stucked to Java 1.6, and I suspect the issue is solved in 1.7.
As Shotwell has this issue before, can you confirm that Shotwell is using Java too?

At least I am trying other java versions and I will see if the issue is stil there.
Thanks and regards.

I think they removed automaximize compiz feature (I am running 13.10), so now it works.

Shotwell is written in Vala ("C encryption"), it translated to C and then compiles.

Pavol, it does not seem to be related to automaximize.
I have this issue 3 times out of 4 with STAR-CCM+ (scientific computation software) and when one instance has this "flaw", every dialog box has it.
So even with not maximized windows (dialog boxes) if the parent window has the issue, the child windows has it too.

After some java tests, it does not change anything with oracle java or open jdk, with 1.6.45, or 1.6.39. Does not seem to be the cause, also according to the fact that Shotwell has no Java.

I have actually some random behaviour, and my previous statement is not true : I have some windows opened normally, with dialog boxes on which I do not see the bottom.
I attached screeshots.
Notice that the bottom of the window (see the maximized one) is a duplicate of the window that was open just before starting, or the desktop wllpapaer if no window was open).

What can I do next to help to focus on the cause?
Thanks
Arnaud

I do not know, but try different WM, it actually might not be a compiz bug.

Pavol, of course I tried other WM, but not on Ubuntu (on OpenSuse). This bug appears only on Unity. I will try on Gnome.

This bug now disappeared for me since 13.10...

I see this bug on current Ubuntu 14.04 in Shotwell and a Wine Windows application. I updated to Ubuntu 14.04 from 13.10 a few days ago.

This bug is quite old and we didn't manage to reproduce it. Therefore I marked it as invalid. If you still experience this problem though, please feel free to re-open the bug. Thank you!