After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640711 - (Maximized) windows are too big, what makes them jump with conpiz
(Maximized) windows are too big, what makes them jump with conpiz
Status: RESOLVED DUPLICATE of bug 267787
Product: evolution
Classification: Applications
Component: general
2.30.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Reported: 2011-01-27 11:45 UTC by Michael Z.
Modified: 2011-01-27 12:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Michael Z. 2011-01-27 11:45:45 UTC

I'm using Gnome on a relatively small screen, and I have the problem with evolution that I can not scale it down to a width of 1024 px. The window is always about 20px too big, so that if I maximize it I cannot see the border (since there is not much in the borders of the window, it is not a problem, but Compiz lets those big windows jump every mouseklick, and it is difficult to aim that way...)

This happens to the main window with all modes, I made the bar on the left and the main area as small as possible, but it is still not enogh. Maby it is possible to adapt the minimal values to the screen resolution.

The settings window is always to high, so that you have to move it with the Alt-key to see the lower part of it. The highest tab that seems to set the minimal height are the general E-Mail settings, so maby adding a scrollbar to the right side would solve the problem.

I had this bug with Ubuntu (newest updates, Evolution 2.30.3) and two laptops.
Comment 1 Akhil Laddha 2011-01-27 12:31:26 UTC
Please use evolution express for small screens. You can launch evolution in terminal 'evolution --express'. This is netbook compatible.

*** This bug has been marked as a duplicate of bug 267787 ***