Bug 198802

I'm astounded to hear this, but nevertheless I can change the font colour of
text in writer in FC-5 from black to red without any problem.

Created attachment 132411 [details]
screen capture showing the bug


Here is a video...

Bizarro!, does format->character->font effects->font color also not do anything ?

From your screen-shot it doesn't look like anything like "high-contrast" for
visually disabled is active. Is there the same behaviour in e.g calc ?

(In reply to comment #3)
> Bizarro!, does format->character->font effects->font color also not do anything ?
> 
same issue font stays black :(
> From your screen-shot it doesn't look like anything like "high-contrast" for
> visually disabled is active. 
what is this? and where can I change it?
>Is there the same behaviour in e.g calc ?
yes...

Created attachment 132414 [details]
new video showing bug

here is the format->character->font effects->font color thing

This is very not normal, and I'm baffled as to what is happening for you. 

Tools->options->openoffice.org->view->icon style of HiContrast would be set,
instead of "automatic" for a visual impaired desktop, but your videos don't look
hicontrast so that's not it.

If tools->autocorrect "apply style" was set then when you pressed return hard
coded formatting would be removed in favour of styles, but your videos also
don't look like that obscure option was set

I can't imagine that the actual font matters, but make sure and try with Luxi
Sans or something. Anything unusual about your setup that you are aware of...

remote X ?, non-default nvidia driver ?, anything else behaving strangely ?

(In reply to comment #6)
> This is very not normal, and I'm baffled as to what is happening for you. 
> 
> Tools->options->openoffice.org->view->icon style of HiContrast would be set,
> instead of "automatic" for a visual impaired desktop, but your videos don't look
> hicontrast so that's not it.
> 
> If tools->autocorrect "apply style" was set then when you pressed return hard
> coded formatting would be removed in favour of styles, but your videos also
> don't look like that obscure option was set
> 
> I can't imagine that the actual font matters, but make sure and try with Luxi
> Sans or something. Anything unusual about your setup that you are aware of...
> 
luxi sans does not work too..
> remote X ?, non-default nvidia driver ?, anything else behaving strangely ?
no local X
yes nvidia driver is used,but the first thing I tryed was disabling it but the
nv driver behaves the same.
no everything else works fine (haven't found any thing so far)

I tested with an other user (root) an here it works fine...
so it must be some setting causing it? how can I reset it to default?

Created attachment 132418 [details]
diff between my and clean config

I have moved .openoffice.org2.0/ and it created a new one.
This time it works fine...
here is the diff beetween both configs (still don't know what have caused it)

+ <node oor:name="Accessibility">
+  <prop oor:name="IsAutomaticFontColor" oor:type="xs:boolean">
+ <value>true</value>

There it is, "tools->options->openoffice.org->accessibility->use automatic font
color for screen display"

Move your old config back, and you'll see that that option was set, that's not
the normal default, so it somehow got turned on. When that's enabled, this is
the expected behaviour. If you move back and disable it again all will be well.

(In reply to comment #9)
> + <node oor:name="Accessibility">
> +  <prop oor:name="IsAutomaticFontColor" oor:type="xs:boolean">
> + <value>true</value>
> 
> There it is, "tools->options->openoffice.org->accessibility->use automatic font
> color for screen display"
> 
> Move your old config back, and you'll see that that option was set, that's not
> the normal default, so it somehow got turned on. When that's enabled, this is
> the expected behaviour. If you move back and disable it again all will be well.
> 

thx!
this was it.. I might have changed it after installing FC5 but can't remember it
(I configured OO the first time after install) ..

At least I *hope* it's not a bug, in that it was manually toggled on, and not
that some bizarre bug autotoggled it on incorrectly.