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 574080 - font too large to fit monitor boxes in gnome-display-properties
font too large to fit monitor boxes in gnome-display-properties
Status: RESOLVED DUPLICATE of bug 549737
Product: gnome-control-center
Classification: Core
Component: Display
2.25.x
Other All
: Normal minor
: ---
Assigned To: Soren Sandmann Pedersen
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-04 14:39 UTC by Robert de Rooy
Modified: 2009-03-05 18:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Robert de Rooy 2009-03-04 14:39:18 UTC 
in gnome-display-properties the font used is too large to fit properly in the pictured displays. The font is being centered in the boxes, resulting in both the left and right hand side of the text being cut off.

Other information:
gnome-display-properties draws some boxes which represent the displays attached to the system. Inside the boxes it puts some text such as Laptop 14", Samsung 21" or Mirror screens. The font used for this text is too large, and since the text is centered in the box both the left and right hand side of the text is cut off, resulting in something like "msung 2" instead of Samsung 21".

This is with Gnome 2.25.90 on Fedora 11 Alpha.
Comment 1 Robert de Rooy 2009-03-04 14:41:59 UTC 
Obviously instead of making the font smaller, the boxes could be made larger. But since I do not think the application is capable of scaling, this might be a problem when in low resolution (640x480) as it would no longer fit on the screen.
Comment 2 Jens Granseuer 2009-03-05 18:17:49 UTC 
Thanks for the bug report. 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 549737 ***