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 597884 - when we scale font with fontconfig rule, titilebar border not get adjusted accordingly
when we scale font with fontconfig rule, titilebar border not get adjusted ac...
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2009-10-09 08:40 UTC by Pravin Satpute
Modified: 2020-11-06 20:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
image showing problem of theme title bar (184.69 KB, image/png)
2009-10-09 08:40 UTC, Pravin Satpute
Details

Description Pravin Satpute 2009-10-09 08:40:16 UTC
Created attachment 145105 [details]
image showing problem of theme title bar

This bug is upstream from Fedora bugzilla, 

https://bugzilla.redhat.com/show_bug.cgi?id=523454

If we set Meera font as Windows Title Fonts in appearences, bottom border of
clearlook and Glossy theme get shifted bit upper, and appear in between title
bar

but this thing happen only with mentioned theme, Crux theme works proper

Meera font has scaling rule for fontconfig.


see attached image for problem, check title bar
Comment 1 Pravin Satpute 2009-10-09 10:44:23 UTC
link for clearlooks theme
http://ftp.gnome.org/pub/GNOME/sources/gnome-themes/2.28/
Comment 2 André Klapper 2020-11-06 20:07:07 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.