Created attachment 47185 [details] database exhibiting issue behaviour I am running Ubuntu 11.04. I have a database created in OOo 3 called "Inventory". When I launch this database in LO 3.3.2 and open the form "USAGE", the form background displays in one of three colors: yellow, red or green depending on the last usage entry. This works as expected in LO 3.3.2. In LO 3.4 RC1, the backgroud color does not display the over entire form - only about three quarters of the form has the correct background, the rest is just white. A second report "TOTALS" from this database exhibits the exact same behavior: the color background is only displayed on 3/4 of form, the rest is white.
This behavior (background color not covering entire form) seems to be a common occurence in LO 3.2 RC1 - I have other datab ases behaving the same way.
This is a problem same as in OOo 3.4Beta1, forms opens in lastly opened mode, not in saved earlier. Forms in Base opens by default in web mode. If you saves one form in print mode, then open another form saved in web-mode, form opens in print mode, which is wrong. See OOo bug 117545, and cws fs34b for solution.
Created attachment 48182 [details] image in background with LibO341
I confirm the bug under Windows. With an image in background, the result is very dirty (see attachment below). Bernard Ribot
Change platform to "All" ?
[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
Hi, It seems work properly with LibO 3.5.5.3 under Windows 7 SP1. Bernard Ribot
Hi Joseph, are you using LO 3.5? The last stable version is 3.5.5. Is bug still in 3.5.5?
This problem is no longer present in LO 3.5