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 664036 - evolution is using the wrong color to mark missspelled words. yellow instead of red
evolution is using the wrong color to mark missspelled words. yellow instead ...
Status: RESOLVED DUPLICATE of bug 660738
Product: evolution
Classification: Applications
Component: Plugins
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-plugin-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-11-14 14:28 UTC by Michael Basse
Modified: 2011-11-14 15:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of the issue about using wrong colors (90.62 KB, image/png)
2011-11-14 14:28 UTC, Michael Basse
Details

Description Michael Basse 2011-11-14 14:28:23 UTC
Created attachment 201371 [details]
Screenshot of the issue about using wrong colors

Hi,
i am not sure if this is an upstream- or ubuntu-bug. So i also created

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/887442

Composing a message with the build-in editor is using the wrong color for missspelled words

In "edit - settings - editor-settings - spellcheck" (translated from the german menu, so i hope i got the right one) is set to "red" to mark missspelled words. But the used color is not red, its yellow. Changing the color in the menu does not have any effect. Its always yellow. Which is (imo) hard to see.
Comment 1 Michael Basse 2011-11-14 14:31:06 UTC
as it seems there is already another launchpad-bug 

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/829351

and maybe a fix


http://git.gnome.org/browse/evolution/commit/?id=d4571114e8b8949922213ac23825075880e59231
Comment 2 Matthew Barnes 2011-11-14 15:11:04 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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