[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 --- Comment #10 from Michael Thompson --- You’ve made a solid point—hardware acceleration being on by default can really mess with stability, especially on less powerful systems. During development of one of my own academic tools, I ran into similar usability concerns. I tested its performance alongside this GPA tool: https://vitgpacalculator.vercel.app/ and noticed how lightweight and stable it remained even with multiple processes running. Definitely something to consider when optimizing user experience. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 --- Comment #9 from Mike Kaganski --- (In reply to launchpad from comment #0) > Expected Result > One of the following solutions is needed: > ... > 2. A system-wide configuration option should exist for administrators to > disable it for all users Already present - same as for anything that is configured in LibreOffice registry. It is explained in the wiki [1] (yes, for a general case, not specifically mentioning the specific property discussed here - but otherwise it would have to mention all the thousands of options available in our expert config dialog). It is also possible to create a configuration extension for any of these options - see [2], and already existing extensions like [3]. [1] https://wiki.documentfoundation.org/Deployment_and_Migration#Post_deployment_configuration [2] https://wiki.documentfoundation.org/images/b/b0/LibreOffice_config_extension_writing.pdf [3] https://extensions.libreoffice.org/en/extensions/show/70063 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 --- Comment #8 from Mike Kaganski --- (In reply to launchpad from comment #0) > LibreOffice Bug Report: Hardware Acceleration Enabled by Default Causes > Serious Usability Issues Abandoned effort: https://gerrit.libreoffice.org/c/core/+/154322 (In reply to launchpad from comment #2) > LibreOffice urgently needs reliable detection to determine whether hardware > acceleration is actually working. Done in 9735a9377b3013943e6a245b5afef57de738a0f6 (already backported to 25.2 for bug 166122). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 --- Comment #7 from V Stuart Foote --- (In reply to Tomaz Vajngerl from comment #6) > Maybe, instead of setting the "UseSkia" to false I would rather set > "ForceSkiaRaster" to true. Yep! That would cover the problem issues of a default launch with testing for Vulkan/Metal vector graphics. Though we'd still be tied to chrome skia libs and its needed driver support for SkWindow/SkCanvas calls, so Deny listing mechanism and better sysadmin support for user profiles and VM instances still would need attention. And with fewer users testing/failing reporting issues with vector rendering, improvements there would stall. Also, for older CPU/GPU & driver sets, are there HA issues to consider for OpenCL? Or is concern with HA just with graphics rendering. Seems like OpenCL fall back has been pretty robust since implemented 10 years back. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 --- Comment #6 from Tomaz Vajngerl --- Maybe, instead of setting the "UseSkia" to false I would rather set "ForceSkiaRaster" to true. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 --- Comment #5 from Buovjaga --- This can be useful: https://wiki.documentfoundation.org/Deployment_and_Migration#Some_tricks_for_post_deployment_configuration Try the LibreOffice registry entry false -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #4 from Heiko Tietze --- You may succeed with a script that applies the flag to the user profile. But we should rather fix the issue causing the trouble. Reliably testing a system for hardware compatibility sounds like a huge challenge to me. Ultimately no topic for UX. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 V Stuart Foote changed: What|Removed |Added Keywords||needsDevEval, needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 V Stuart Foote changed: What|Removed |Added CC||[email protected] See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||6122 --- Comment #3 from V Stuart Foote --- (In reply to launchpad from comment #2) > LibreOffice urgently needs reliable detection to determine whether hardware > acceleration is actually working. If it's not, LibreOffice should > automatically disable it—without forcing end users to troubleshoot or > navigate unintuitive settings. > Actually already had very effective testing around support of Vulkan (and before that for OpenGL), now being done with Google chromium skia libs. With fall back to skia based raster framing. Or manual de-selection of the skia libs, for fallback to 'default' GDI+ based rendering libs--CPU only or with CPU controlled HA. Those skia lib releases, external to project, were updated from m116 to m130 for the 25.2.0 builds. And some as yet undetermined fact of the testing framework has slipped. It is a routine issue, and once fully identified would likely make it into the 25.2 branch in an incremental patch release. > Until that detection is fully reliable, hardware acceleration should be > disabled by default. Please make this change in the very next release. Well that won't happen. More to the point to identify what's changed in the skia skwindow call when Vulkan test for a non-denylisted device is run and fails. Also, the denylist for Virtual devices should be more robust, specifically VMWare VMSVGA or MS Hypervisor VM Bus Video Device should be deny listed. And there is the possibility the skia based software rendering is also degraded on marginally supported GPUs and vendor drivers. Too soon to be certain. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 --- Comment #2 from [email protected] --- LibreOffice urgently needs reliable detection to determine whether hardware acceleration is actually working. If it's not, LibreOffice should automatically disable it—without forcing end users to troubleshoot or navigate unintuitive settings. Until that detection is fully reliable, hardware acceleration should be disabled by default. Please make this change in the very next release. Additionally, when hardware acceleration prevents LibreOffice from launching, and an administrator disables it, that change should apply to all users on the machine, not just the admin account. If it fails for one user, it will fail for all. Forcing every user to repeat the same workaround is unacceptable. I cannot emphasize this enough: PLEASE DISABLE HARDWARE ACCELERATION BY DEFAULT IN THE NEXT RELEASE, AND ONLY RE-ENABLE IT BY DEFAULT ONCE RELIABLE AUTO-DETECTION IS IN PLACE. For more emphasize, see here: https://neartalk.com/thao/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #1 from Buovjaga --- This is probably bug 166122 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 166507] Hardware Acceleration Enabled by Default Causes Serious Usability Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=166507 [email protected] changed: What|Removed |Added URL||https://superuser.com/quest ||ions/1896695/ -- You are receiving this mail because: You are the assignee for the bug.
