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 765591 - Preferences: Account Editor: port numbers are overlapping dialog borders
Preferences: Account Editor: port numbers are overlapping dialog borders
Status: RESOLVED DUPLICATE of bug 764802
Product: evolution
Classification: Applications
Component: Shell
3.20.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2016-04-26 10:09 UTC by Christian Stadelmann
Modified: 2016-04-26 17:33 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot of "Account Editor" dialog with broken widget size(s) (41.61 KB, image/png)
2016-04-26 10:09 UTC, Christian Stadelmann 		Details

Description Christian Stadelmann 2016-04-26 10:09:03 UTC 
Created attachment 326745 [details]
Screenshot of "Account Editor" dialog with broken widget size(s)

Steps to reproduce:
1. start evolution
2. open Edit → Preferences
3. for any account, open Account Editor
4. go to tab "Receiving Email" or "Sending Email"

What happens:
The port number field is overlapping dialog borders. On x11 backends it is cut off, on wayland backends it is partially drawn outside the dialog.

What should happen:
All widgets should be drawn inside the dialog without being cut off. There is enough free space in the text field for specifying server hostname.

Affected version:
gtk3-3.20.3-1.fc24.x86_64
evolution-3.20.1-1.fc24.x86_64

Additional info:
This issue was not present with 3.18.x gtk3 and evolution.
See attached screenshot.
Comment 1 Milan Crha 2016-04-26 17:33:53 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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