https://bugs.documentfoundation.org/show_bug.cgi?id=58358
--- Comment #55 from Renato Miró <rezg...@mail.com> ---
(In reply to John L. ten Wolde from comment #54)
> (In reply to Renato Miró from comment #53)
> Hi Renato.
Hi, John, how do you do?
> The description of your issue is so similar to mine and others
> make sure that your sub-pixel rendering is disabled:
> KDE System Settings > Application Appearance > Fonts > Use Anti-Aliasing
> [Configure...]
Sorry, didn't work in my case. I guess this "winmodem"-style video card is way
more primitive than whatever hardware you may have. To me, that Thomas guy is
starting to look like a hero.
> but given the choice between sub-pixel rendering versus hardware
> acceleration, I'd choose to dump sub-pixels in order to keep hardware
> acceleration every time.
I would, too, but this chip only uses EXA ("Option AccelMethod not used" in the
X log). I tried to select XAA, but got that message. Besides, frankly,
accelerated means glxgears gives 99 fps instead of 81.
> For a more verbose treatment on all this, see my step-by-step report at Bug
> 69011. Note I wrote that report while running Mageia 3 and much of the
> flakiness KDE was exhibiting at that time has since been ironed out.
I've read it to check whether I did the right steps. Though in my case, KDE is
choosing Xrender even when I opt for OpenGL 1.2 -- which means my problems are
not really about GL.
> Best of luck.
Likewise, my friend. For your information, I'm using the document
"BH3501-IntroductiontoBase.odt" (just search "BH3501 filetype:odt" on Google).
Scrolling the first page already clearly creates artifacts.
Off-topic, but perhaps related: I've read elsewhere that "unusual" DPI settings
can also lead to problems. Not sure about it, but the theory goes like
rescaling 96DPI fonts to, say, 117 DPI could produce truncation errors (because
we can't have 0.5 pixel) and thus the recomendation was to use more exact
multiples like 96 itself or 120 (=96 x 1.25). Don't know if that makes any
difference. Some three years ago I had problems with fonts in Firefox, now I
don't.
> P.S. I've still got my fingers crossed that when the remaining issues with
> OpenGL get sorted and we Linux users can actually enable it again -- for
> examples see Bug 97904 and Bug 99299 -- all this will be just an ugly
> memory. In Bug 97904, comment 4, Caolán committed an OpenGL patch to 5.1.2,
> but I haven't noticed a difference so far. I'm hoping it works in the 5.2.x
> branch.
Not that it helps in your case, but for the record I use Libreoffice a lot with
Intel integrated video and old Nvidia Geforce cards (10+ year old!) and can say
without any chance of mistake that I have not had any kind of problem before
like the present one.
Also, check the OpenGL version which your h/w accepts. I once tried to use
OpenGL 2.0 with a board which would only accept 1.2 with disastrous
consequences; in the same vein, don't deactivate OpenGL (Mesa) and try to run
Libreoffice with that "Use OpenGL..." option activated. It will crash
repeatedly at start until you edit a *.xcu file in ~/.config/libreoffice to
change it back to false.
IMHO it's possible that it is the case of a bad interaction between the
hardware+driver set and some low-level video access by Libreoffice. It's even
possible there's no bug in Libreoffice but rather some shortcoming in these
more, erm, "exotic" video cards -- which other packages learned to avoid but
which is still not worked around by LO.
Thanks, again!
--
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
