https://bugs.documentfoundation.org/show_bug.cgi?id=112305
--- Comment #8 from Mike Kaganski <mikekagan...@hotmail.com> ---
(In reply to V Stuart Foote from comment #7)
> Not sure it is appropriate, or even feasible, to be handled in Safe Mode.
> Especially if the failure is AMD hardware driver related for rendering
> DirectX DirectWrite Direct2D text. Any Safe Mode work would have to signal
> the OS to force non-accelerated CPU rendering, or alternatively force OpenGL
> rendering.
>
> And this really seems a corner case for users afflicted with AMD GPUs and
> balky DirectX and OpenGL drivers--it is not common.
Let me put it form the PoV of a user:
the program has a problem. It provides an option to start in a mode dedicated
to workaround issues, and pin down specific problems - yet, the mode suffers
from the same problem, and thus is useless.
This, actually, is more deep problem: the Safe mode wizard uses the same
LibreOffice rendering machinery as LibreOffice itself (well, with some specific
configuration known to be mostly safe), so any problem affecting that
configuration will make the wizard useless.
My feeling is that the wizard should be more low-level, and rely on basic OS/WM
features, without need to rely on possibly problematic code. So, my point is
not to disable/enable some other flags in LO rendering machinery, but bypass it
entirely.
This is offtopic here, though.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
