System: AMD A4-5000 (internal graphics) OS: Windows 10 x64 Build 10586 AMD Driver: 16.3.2 (LibreOffice 4.4.7.2 is running perfectly fine) I tested LO 5.1.2.2. There were always some graphical glitches with text and draw files. And I couldn't open more than one of my old files on this new version. The second window keeps crashing. I tested different file type combinations(odt, ods, odg). I also removed the %AppData% Folders of LO and reinstalled. For my work setup I need 5 LO files constantly opened. One ods file, 2 odt and 2 odg. So I recreated those files with placeholder text and my layout (one jpg embedded). I got nasty text glitches when I created odg aside of odt files on the other file while it was opened. ods files were fine tough. I'll gladly help on debugging this. I think this problem is a bit obscure. My old file layout dates back to 2011, so they're pretty old. And got constantly changed and saved every day. (Also I had problems while installing: the installer said, that the process 'Explorer.exe' locks up files. Maybe this is a hint.) Thanks. Daniel
Try it with the OpenGL rendering disabled... Tools -> Options -> View: Use OpenGL for all rendering (on restart) If that clears things up a bit, post details from your opengl_device.log in the case directory of your user profile.
Created attachment 124728 [details] opengl_device.log > Tools -> Options -> View: Use OpenGL for all rendering (on restart) Solves the issue for now. (First deinstallation then install also removes the Explorer.exe blockade.)
OK, glad that gets you functional again. Seems like your AMD Radeon HD 8330 on Windows 10 should support OpenGL requirements. Adding this to the bug 93529 tracker. DriverVersion: 16.150.2211.0 DriverDate: 3-21-2016 DeviceString: AMD Radeon HD 8330 The devs have a "blacklist" mechanism for Windows builds intended to prevent activation of OpenGL rendering with sub-par GPU and drivers, but otherwise set it active by default. With the wide mix of GPU and drivers, and different levels of OpenGL support in the support Windows OS (XP, Vista, 7, 8, 8.1 and 10) the "blacklist" is proving to be a challenge especially for combinations that are just on the margin of functioning, or should function but simply don't. Some Windows based users are ending up with OpenGL enabled and should disable it and revert to simpler OS and GPU hardware rendering. OpenGL rendering is disabled by default for Linux builds. And must be manually activated--folks decide then if it functions correctly for them. May end up doing the same for the Windows builds. The simple fact is some combinations of GPU OS and drivers will never function correctly with the OpenGL based accelerated rendering being implemented, presumably correctly, by LibreOffice.
Would be nice to have screenshots of the glitches.. maybe something we can fix.
Sorry I can't reproduce it right now, have to work away from the computer. But I can describe it: they appeared irregular over the text and looked like Tetrisshapes. I could remove them by deleting the letter under or beneath the squares. The size was about half of the letter size. But more annoying was that I couldn't open more than one of my old files with GL enabled. LO was extremely laggy. Yes those files are a mess. (The content.xml has alot of <text style span>s inside the words. Not by intension, just a 5 year old files.) e.g. Hilko He<text:span text:style-name="T10">gewisch</text:span> <text:span text:style-name="T9">(Winemaker)</text:span>. Thanks for your fast and on point help. Have a nice weekend Daniel
Without some clear description of what actually happens, and reproduction instructions, and/or sample documents, there is very little that can be done here.
For what it's worth, a fresh build of LibreOffice 5.1 seems to work OK with OpenGL in use on my Windows 10 box, with an AMD A10-7800, and the same driver version as in the attached opengl_device.log.
Based on comment 7, let's close it as WORKSFORME for the moment. Daniel - if you happen to see the artefacts again with the newest LibreOffice 5.1.3 (you can try the release candidate from http://dev-builds.libreoffice.org/pre-releases/win/x86/), please reopen this bug, and attach screenshots of the problem. Thank you for your help!