Created attachment 125561 [details] screenshot of abovementioned problem Hello! The input line in Calc is acting rather strangely...it's displaying block characters instead of the numbers. If you click on the cell it's fine, but the input line is not fine.Please refer to screenshot to get an idea of what I'm describing. Thanks! Ryan M Andres
disable open GL
*** Bug 100280 has been marked as a duplicate of this bug. ***
Hi! I saw your other report as well, did disabling OpenGL fix the issue? If it did, would you mind attaching this log file: C:\Users\<user name>\AppData\Roaming\LibreOffice\4\cache\opengl_device.log Also, did the bug happen with an empty document/any document, or only in specific cases? While the workaround seems to have fixed the issue, others might be having the same problem, so it would be nice to know a bit more about it. Thanks!
Created attachment 125571 [details] OpenGL device log Ryan sent me his OpenGL device log. It seems to be an Intel Haswell IGP. He also wrote that the bug appeared even in new spreadsheets in Calc (or in any opened spreadsheet).
Ryan confirmed that it's a Haswell IGP, CPU model is i5-4210U. Michael, I saw a similar device (AdapterDeviceID: 0x0a16) being blacklisted as a solution to a different bug (bug 97726). While that might "solve" this as well by defaulting to non-GL rendering, I'm not sure that's what we should rely on, Haswell's OpenGL support should be mature enough for this to be considered a bug after all.
afaics the opengl_blacklist_windows.xml on master wouldn't blacklist the device in comment #4 that's the extent of my knowledge about our OpenGL implementation so maybe CC somebody who knows something about it instead
Thanks for the clarification, Michael. I didn't know how the blacklisting worked exactly, but can now see that in the case of the aforementioned (otherwise unrelated) bug report the Intel IGP is blacklisted based on an older driver version.
Confirmed based on the following reddit threads: https://www.reddit.com/r/libreoffice/comments/4mt3yo/help_garbled_text_in_libre_calc/ https://www.reddit.com/r/libreoffice/comments/4noe18/calc_windows_ive_no_idea_what_the_cause_of_it_is/ Another OpenGL device log: DriverVersion: 20.19.15.4360 DriverDate: 12-21-2015 DeviceID: PCI\VEN_8086&DEV_1616&SUBSYS_F8401179&REV_09 AdapterVendorID: 0x8086 AdapterDeviceID: 0x1616 AdapterSubsysID: 0xf8401179 DeviceKey: System\CurrentControlSet\Control\Video\{CAC75DC4-5212-4335-8C63-B7DE14F938AE}\0000 DeviceString: Intel(R) HD Graphics 5500 What is somewhat conflicting is that for Ryan the bug occurred with empty documents as well, but it didn't for the person who gave this device log.
Created attachment 125640 [details] Open GL Device Log
Comment on attachment 125640 [details] Open GL Device Log https://www.reddit.com/r/libreoffice/comments/4mt3yo/help_garbled_text_in_libre_calc/
Comment on attachment 125640 [details] Open GL Device Log This link leads to a screenshot of the same issue happening to me. https://www.reddit.com/r/libreoffice/comments/4mt3yo/help_garbled_text_in_libre_calc/
Created attachment 125799 [details] Actual screenshot extracted from the .odt in the first attachment
Could those who are able to reproduce this bug please follow these instructions to get a detailed log file that might help in fixing the problem: From http://dev-builds.libreoffice.org/daily/master/Win-x86@39/ , download the .msi file in the latest subdirectory. For instance, today, that would be master~2016-06-21_01.16.33_LibreOfficeDev_5.3.0.0.alpha0_Win_x86.msi. Open a Command Prompt, and change directory to where the .msi was downloaded (in my case, would typically be c:\Users\Tor\Downloads) Enter the command: msiexec /a master~2016-06-21_01.16.33_LibreOfficeDev_5.3.0.0.alpha0_Win_x86.msi (Adapt the file name as necessary, of course.) This will not replace your existing LibreOffice installation but create a so-called "server image" or "administrative image" of an installation. When the installer asks for where to place it, choose some fresh empty directory. For instance, in my case, I chose c:\Users\Tor\Desktop\master~2016-06-21_01.16.33 . In Command Prompt, first cd to that directory, and enter the following three commands: cd program set SAL_LOG=+INFO.vcl.opengl+WARN soffice.exe --calc 2>soffice.log Then try to reproduce the issue. If you see it, don't do anything else, just quit LibreOffice. Please attach the soffice.log file to this bug.
Unfortunately I cannot reproduce the bug. I have tried forcing openGL. Maybe my .ods file is healed. Does anyone else have a file that I can open to reproduce this bug?
Setting to NEEDINFO until we get more information, like a SAL_LOG output file as described above.
*** Bug 100229 has been marked as a duplicate of this bug. ***
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170131
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170301