We recently upgraded our SunRay software (on Solaris) to Version 4.2 and everything worked fine until some of our users started to tell us that when they turned text "red" in either Writer or Spreadsheet that the text turned "blue" ... and vice-versa ... Opening and displaying Pictures show the correct colours, and printing documents makes the text come out in the correct colour. the colour "chooser" on the icon bar shows the correct colour. I know that this affects OpenOffice, and not LibreOffice per ce, but since you had a shared code base and LibreOffice is being actively worked on (I'm still hoping for a Solaris Package but understand there are issues) ... My colleague asked for Support on the SunRay Forums and got this response: > Hi > > I have recently upgraded from SRSS 4.0 to 4.2. I am running Solaris 10 > 10/09 s10x_u8wos_08a X86 in a FOG > Everything is fine except just one thing. When I open a either a new or > existing document in Openoffice 3.2 and change the font colour, the > colour mapping is wrong. I choose blue font, the document displays red, > I choose turquoise1, it displays yellow. and so on. The chosen colour is > OK in the toolbar. If I print the page to a colour printer the colours > are correct > > Colour mappings seem fine if I open up an image or browse the web. > > If I go to the SunRay server console and open up a document then > OpenOffice works fine. This rules out > a problem with OpenOffice No, just the opposite. It points the finger squarely at OpenOffice. In the X server, different framebuffers are allowed to implement different color packing orders, and inform the X server of the proper RGB byte masks to use. Applications are required to query the server for the proper RGB mask, and use it. However, 90% of framebuffers these days implement an RGB byte order, whereas Sun Ray implements a different order (legitimately). Sometimes, app writers get lazy, and don't bother to query the mask and handle it as the X API specifies they should. This works for most hardware these days, but breaks for exceptions like Sun Ray. That's a bug in the application. In this case - OpenOffice. They're not following the X API properly. -Bob
run it with SAL_DISABLE_CAIROTEXT=true just to rule in or out that text rendering branch out
(In reply to comment #1) > run it with SAL_DISABLE_CAIROTEXT=true just to rule in or out that text > rendering branch out I defined that variable in /opt/openoffice.org3/program/soffice and the problem still persists. Thanks.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
(In reply to comment #3) > [This is an automated message.] > This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it > started right out as NEW without ever being explicitly confirmed. The bug is > changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back > to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 > prereleases. > Details on how to test the 3.5.0 beta1 can be found at: > http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 > > more detail on this bulk operation: > http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html Problem was located in OpenOffice3.2 on Solaris 10, I cannot test with the latest LibreOffice at the moment (Currently not packaged for Solaris 10) Please leave in NEEDINFO till I can test with LibreOffice.
Please, verify if package already exist
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian