Maximized evolution window is not maximized

[David Ayers]

When maximizing Evolution on Oneiric the window is not maximized.
(see screen shot)

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: evolution 3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Nov 5 17:53:18 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, no user)
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

[David Ayers (ayers)]

Actually the window is not maximized at all, only the window decorations are removed. Not sure whether this a Unity or Evolution issue.

[David Ayers (ayers)]

I'm testing this in VM with a maximum resolution is 1024x768 yet it seems Evolutions main Window cannot be sized narrow enough to fit into the screen. I thought this could be relevant.

The effect of maximizing is that the Window decorations are removed (i.e. the menu is placed into the global menu together with the close/minimize/maximize button but the rest of the content remains where it was before pressing the maximize button. This does not happen on higher resolutions on a USB installation of Oneiric that I have. But reducing the screen size here to 1024x768 doesn't have the same affect.

I'll report back if I find a something else that may be causing this issue.

[David Ayers (ayers)]

Indeed... if I set the video device in virt-manager from cirrus to vmvga I am able to select higher screen resolutions within the vm. When the vm has a higher screen resolution, evolution maximizes as expected. So this is actually interaction issue between unity and evolution for expecting too much screen real estate.

So I would say that this is indeed related to Bug #23810 but not necessarily a duplicate of it. I think unity should be able to deal with applications that expect higher resolutions even if evolution is not one that shouldn't be expecting it... so maybe this should be reassigned to unity?