Apache OpenOffice (AOO) Bugzilla – Issue 124558
Gallery preview view looks empty
Last modified: 2017-05-20 10:35:32 UTC
Seen with AOO410m14(Build:9760) - Rev. 1582709 on Window 7. Start a Draw document and open Gallery. Make sure, you have chosen the preview image view. Notice the view is empty. When you switch to file name view, you can see, that the gallery elements are still there and you can use them.
The gallery elements are in the preview, and you can drag and drop them to the document, gut they indeed are not visible. Preview appears with double click or <Enter>
Was still ok with server installation of "AOO 4.1.0-dev – English UI / German locale - [AOO410m14(Build:9760) - Rev. 1577236 2014-03-15]" on German WIN7 Home Premium (64bit)", own separate user profile All AOO applications affected!
I could not reproduce the described defect in AOO 4.1.0 Beta. I can reproduce the described defect in recent build bot installation set (rev. 1582709) and in my own recent build from branch AOO410. --> I think this issue is relevant for the 4.1.0 release
Confirmed on Debian with the latest snapshot based on 1582710.
Could not reproduce on the AOO410 beta itself (AOO410m14(Build:9760) - Rev. 1572596) and not on trunk version (AOO410m14(Build:9760) - Rev. 1578923), getting newest trunk. Are you sure about 'own recent build from branch AOO410', could you double-check? The added changes were very rare and controlled and I am not aware of anything that could touch window refresh stuff. Can anyone else, any suspects?
(In reply to Armin Le Grand from comment #5) > Could not reproduce on the AOO410 beta itself (AOO410m14(Build:9760) - > Rev. 1572596) and not on trunk version (AOO410m14(Build:9760) - Rev. > 1578923), getting newest trunk. Are you sure about 'own recent build from > branch AOO410', could you double-check? The added changes were very rare and > controlled and I am not aware of anything that could touch window refresh > stuff. Can anyone else, any suspects? Unfortunately, I am sure.
Getting fresh AOO410 trunk and building...
Reverting revision 1582689 fixes this problem.
This has probably the same root cause as bug 124555.
fixed by the changes made for bug 124555