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 660738 - Font changes ignored since 3.2
Font changes ignored since 3.2
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Shell
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 662107 662577 663997 664036 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-10-03 03:54 UTC by Yves-Alexis Perez
Modified: 2011-11-14 15:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
evo patch (3.41 KB, patch)
2011-10-21 12:08 UTC, Milan Crha
committed Details | Review
evo patch (3.41 KB, patch)
2011-10-21 12:14 UTC, Milan Crha
committed Details | Review

Description Yves-Alexis Perez 2011-10-03 03:54:32 UTC
Hey,

starting with 3.2 (and the switch to gsettings, I guess), monospace fonts are not displayed at the correct size (they're too huge). I was using the “use the same as other applications” in 3.0- with the setting set in gconf.

Now, I don't have that configured in gsettings (I don't run GNOME so I didn't figured out yet how to do that) so I've switched to manual setting in evolution, but selecting a monospace size doesn't change anything, it's still using the same large size.
Comment 1 Yves-Alexis Perez 2011-10-03 04:14:44 UTC
Note running:


gsettings set org.gnome.desktop.interface monospace-font-name "Monospace 5"

fixes the font size (wether “use same font size” is selected or not).

So it seems that the checkbox doesn't do anything anymore
Comment 2 Yves-Alexis Perez 2011-10-03 04:15:06 UTC
Note running:


gsettings set org.gnome.desktop.interface monospace-font-name "Monospace 5"

fixes the font size (wether “use same font size” is selected or not).

So it seems that the checkbox doesn't do anything anymore
Comment 3 André Klapper 2011-10-03 09:22:51 UTC
bug 660551 might be related (same issue?)
Comment 4 Yves-Alexis Perez 2011-10-03 16:12:31 UTC
I don't think so, it seems that setting the setting to a same value worked for that user. In my case selecting anything there doesn't work, the only way to change this is to set it in gsettings (and it works wether or not the checkbox is ticked),
Comment 5 Matthew Barnes 2011-10-03 22:47:41 UTC
Is evolution emitting any WARNING or CRITICAL messages to the terminal?
Comment 6 Milan Crha 2011-10-21 12:08:18 UTC
Created attachment 199631 [details] [review]
evo patch

for evolution;

I also realized, when switching to Gnome 3.2, that spell error color in composer is yellow, not red, as it used to. Thus I found couple more issues which are fixed by this patch:
 - wrong colors - gtk's css parses only #rrggbb colors, from those encoded
   by gdk_color_to_string(), which are #rrrrggggbbbb, it takes only the first
   8 letters (not including the pound), thus it decodes #rrrrgg as the full
   color, so for full red FFFF00000000 is used FFFF00, which is yellow
 - 'fixed-font-name' is expected as string, thus quotes needed
 - changes in preferences are not propagated immediately (the style isn't
   recreated)
Comment 7 Milan Crha 2011-10-21 12:13:55 UTC
Created commit d457111 in evo master (3.3.1+)
Created commit c8abded in evo gnome-3-2 (3.2.2+)
Comment 8 Milan Crha 2011-10-21 12:14:40 UTC
Created attachment 199632 [details] [review]
evo patch

for evolution;

There was a typo in the patch, missing comma :-/
Comment 9 Milan Crha 2011-10-21 12:26:51 UTC
*** Bug 662107 has been marked as a duplicate of this bug. ***
Comment 10 Akhil Laddha 2011-10-24 09:54:23 UTC
*** Bug 662577 has been marked as a duplicate of this bug. ***
Comment 11 Akhil Laddha 2011-11-14 03:51:21 UTC
*** Bug 663997 has been marked as a duplicate of this bug. ***
Comment 12 Matthew Barnes 2011-11-14 15:11:04 UTC
*** Bug 664036 has been marked as a duplicate of this bug. ***