Description: When a word in the existing document is changed or marked, the former display persists and all is illegible Steps to Reproduce: 1. Take an existing Document. 2. Change a Word 3. When you change the size of the window and you go back after, then all is clear Actual Results: illegible Expected Results: as in the former versions Reproducible: Always User Profile Reset: No Additional Info: Windows 7 Libreoffice 7.0.1.2
Created attachment 165241 [details] Sreenshot
Please post the hardware details about your Windows system. Run msinfo32.exe and copy content of the summary panel, and also of the Components -> Display panel. Also, do you have trouble if you disable the Skia rendering? Test it by reverting to legacy Windows GDI rendering. Done from main menu launching the LibreOffice Tools -> Options -> LibreOffice -> View panel. And there "uncheck" the 'Use Skia for all rendering' box, and restart LibreOffice. Does that improve the rendering?
First of all I have to tell you that I use LO 7.0.1.2 also on a linux-computer (Kubuntu 20.04 AMD64) WITHOUT any problems. ******************************************************************************* Now about the windows computer: Betriebssystemname Microsoft Windows 7 Ultimate Version 6.1.7601 Service Pack 1 Build 7601 Zusätzliche Betriebssystembeschreibung Nicht verfügbar Betriebssystemhersteller Microsoft Corporation Systemname AMD-NEU Systemhersteller Gigabyte Technology Co., Ltd. Systemmodell GA-A75M-D2H Systemtyp X86-basierter PC Prozessor AMD A8-3850 APU with Radeon(tm) HD Graphics, 2900 MHz, 4 Kern(e), 4 logische(r) Prozessor(en) BIOS-Version/-Datum Award Software International, Inc. F5, 03.11.2011 SMBIOS-Version 2.4 Windows-Verzeichnis C:\Windows Systemverzeichnis C:\Windows\system32 Startgerät \Device\HarddiskVolume1 Gebietsschema Österreich Hardwareabstraktionsebene Version = "6.1.7601.24545" Benutzername XXXXXXXXX Zeitzone Mitteleuropäische Sommerzeit Installierter physikalischer Speicher (RAM) 4,00 GB Gesamter realer Speicher 3,25 GB Verfügbarer realer Speicher 1,53 GB Gesamter virtueller Speicher 6,49 GB Verfügbarer virtueller Speicher 4,79 GB Größe der Auslagerungsdatei 3,25 GB Auslagerungsdatei C:\pagefile.sys *************************************************************** And YES, the unchecking of the Skia-rendering did it ! No
OK, the embedded AMD HD 6550D GPU on the A8-3850 APU is going to have marginal behavior. You didn't post the driver details from the component-> display. But expect you have the last release... The last AMD "legacy" Catalyst driver from Jul 2015 is 15.7.1 (WHQL) or you can try the Crimson driver from Mar 2016 or 16.2.1--but I could not determine level of Skia support for either. You may be limited to no use of Skia rendering, and we'll need the GPU/driver pair establish a denylist entry for your hardware so it does not attempt Skia rendering. Needinfo is still to you to determine your driver details.
Created attachment 165299 [details] Drivers fom the Catalyst-center
If you get the infos twice, it's because of my internet connection. If display in german is "Anzeige", then look here: Name AMD Radeon R7 200 Series PNP-Gerätekennung PCI\VEN_1002&DEV_683D&SUBSYS_E214174B&REV_00\4&2E5D29BF&0&0010 Adaptertyp AMD Radeon Graphics Processor (0x683D), Advanced Micro Devices, Inc.-kompatibel Adapterbeschreibung AMD Radeon R7 200 Series Adapter-RAM 1,00 GB (1.073.741.824 Bytes) Installierte Treiber aticfx32.dll,aticfx32.dll,aticfx32.dll,atiumdag.dll,atidxx32.dll,atiumdva.cap Treiberversion 24.20.13019.1008 INF-Datei oem56.inf (Abschnitt ati2mtag_R575A) Farbebenen Nicht verfügbar Farbtabelleneinträge 4294967296 Auflösung 1600 x 900 x 60 Hz Bits/Pixel 32 Speicheradresse 0xD0000000-0xFEBFFFFF Speicheradresse 0xFDF80000-0xFDFBFFFF E/A-Port 0x0000DE00-0x0000DEFF IRQ-Kanal IRQ 4294967278 E/A-Port 0x000003B0-0x000003BB E/A-Port 0x000003C0-0x000003DF Speicheradresse 0xA0000-0xBFFFF Treiber c:\windows\system32\drivers\atikmpag.sys (24.20.13019.1008, 437,88 KB (448.392 Bytes), 26.09.2018 05:14) Note that I did an upgrade of the drivers after reading your post No
(In reply to n.lederbauer from comment #6) > Note that I did an upgrade of the drivers after reading your post > Interesting, so you have a discrete AMD R7 200 series GPU, that should be able to handle both Skia Vulkan and Skia (software only) raster rendering. More recent drivers should help there as well. Could you please have another go at running with Skia Vulkan rendering, and post up the details from the skia.log -- it should be located in "C:\users\<username>\AppData\Roaming\LibreOffice\4\cache" Likwise, try a run with Vulkan disabled using Skia check-box, but also the 'Force Skia software rendering' check-box.
1) skia.log RenderMethod: vulkan Vendor: 0x1002 Device: 0x683d API: 1.1.77 Driver: 2.0.49 DeviceType: discrete DeviceName: AMD Radeon R7 200 Series Blacklisted: no 2) opengl-device.log DriverVersion: 24.20.13019.1008 DriverDate: 9-25-2018 DeviceID: PCI\VEN_1002&DEV_683D&SUBSYS_E214174B&REV_00 AdapterVendorID: 0x1002 AdapterDeviceID: 0x683d AdapterSubsysID: 0xe214174b DeviceKey: System\CurrentControlSet\Control\Video\{53708AA3-74B1-4FCF-B522-CD8AC0BC17B2}\0000 DeviceString: AMD Radeon R7 200 Series 3) skia.log RenderMethod: raster Compiler: Clang Note that in my country it is 02:02 and I go to bed now.
[Automated Action] NeedInfo-To-Unconfirmed
??? more information please!
https://gerrit.libreoffice.org/c/core/+/102290
(In reply to n.lederbauer from comment #10) > ??? > more information please! OK, it gets a little tricky from here. The patch noted in comment 11 will prevent your AMD Radeon R7 200 series GPU attempting Skia Vulkan hardware acceleration until a newer AMD driver is installed. But, this patch will currently only be found on the nightly builds of the master branch, and a 7.1 release some months from now. Which means for testing you would need to download [1] and install in parallel--using "msiexec.exe /a" administrative install [2] of the nightly package. We'd love to know if the denylist entry for the driver resolves issue with the document refresh. =-ref-= [1] for 32-bit https://dev-builds.libreoffice.org/daily/master/Win-x86@39/ or for 64-bit https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/ [2] https://wiki.documentfoundation.org/Installing_in_parallel/Windows pay attention to the section "Version 3.5 and newer" and also setting the "User configuration" for using the administrative install. Done that way, install is self contained and you can simply delete it when finished with testing without disrupting your system.
OK I don't think I'm a good testing person since my english skills are not so good. And then, after the update of my (old) system - new driver -> radeon-software-adrenalin-18.9.3-minimalsetup-181005_32bit I had no problems with the rendering in all three cases: 1. Skia 2. no Skia ( openGL ) 3. forced Skia (see Comment 8) So for me the problem is resolved. As I think that LO used Skia-rendering also in previous releases and I had only problems with LO 7.0.1.2, which was due to an outdated driver, this was a minor problem and I thank you all for your help. On my Linux LO there is no Skia, no Vulcan, only openGL. No
Luboš Luňák committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3f620e74aa00e34f773d97e9480a6532d9e8863e blacklist amd driver with vulkan version <= 2.0.49 (tdf#136553) It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Luboš Luňák committed a patch related to this issue. It has been pushed to "libreoffice-7-0": https://git.libreoffice.org/core/commit/815aed09bb91aea2e8dd54f4b767505aa273cc3f blacklist amd driver with vulkan version <= 2.0.49 (tdf#136553) It will be available in 7.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.