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 781858 - GNOME Shell needs way for users to customize default font
GNOME Shell needs way for users to customize default font
Status: RESOLVED DUPLICATE of bug 688288
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-04-27 18:35 UTC by Jeremy Bicha
Modified: 2017-04-27 19:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeremy Bicha 2017-04-27 18:35:01 UTC 
GNOME Shell is not written in GTK+ and does not respect the GTK+ default font settings. This is confusing when a user tries to change the Interface Font in Tweak Tool>Fonts but it doesn't affect the biggest part of the GNOME interface.

Other Info
----------
Ubuntu 17.10 Alpha is currently using the Ubuntu font instead of Cantarell. This is done by simply patching the gnome-shell css. It would be nice if there was an easy way for users to explicitly choose to use Cantarell but just because a user has Cantarell installed does not mean they want to use it instead of the Ubuntu font for GNOME Shell.

More
----
It would also be nice if there was a way to system-override the default font setting so that if a user has a certain configuration package installed, GNOME Shell would use the font specified in that package. This kind of customization works well for stuff that uses gsettings.
Comment 1 Jeremy Bicha 2017-04-27 18:37:24 UTC 
See https://bugzilla.gnome.org/767294
Comment 2 Florian Müllner 2017-04-27 19:02:24 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 688288 ***