Bug 150912 - Italic and bold graphic glitch with Noto fonts on Arch Linux KDE Plasma when scrolling or editing text
Summary: Italic and bold graphic glitch with Noto fonts on Arch Linux KDE Plasma when ...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.3 release
Hardware: All Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: KDE, KF5
  Show dependency treegraph
 
Reported: 2022-09-11 17:51 UTC by Marcool
Modified: 2022-10-31 08:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screencast of graphical bug with Noto fond italic/bold (4.52 MB, image/gif)
2022-09-11 17:52 UTC, Marcool
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcool 2022-09-11 17:51:55 UTC
Description:
In a brand new document, with a paragraph of text in Noto font, the bold and italic aspect of a word is not consistently maintained when scrolling or editing the line with a bold word. Please see attached screencast for illustration.



Steps to Reproduce:
In a new writer document with a paragraph of text
1. Set font to "Noto Sans" (or any other Noto font)
2. Select a word in the text
3. Toggle bold and/or italic for that word
4. Scroll the word off the screen, then back again.
5. Place a space after the word and remove it.

Actual Results:
The bold and/or italic "disappears" then reappears" as one scrolls it in and out of view, or places and then removes the space after it.

Expected Results:
Bold and/or italic should just stay as they are.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
This does not happen with Liberation fonts, for instance. Haven't tested any more exhaustively to see which fonts do, which fonts don't...

OpenGL information:

OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.1.7
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.1.7
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.1.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
Comment 1 Marcool 2022-09-11 17:52:54 UTC
Created attachment 182392 [details]
screencast of graphical bug with Noto fond italic/bold
Comment 2 Roman Kuznetsov 2022-10-04 13:43:13 UTC
No repro in

Version: 7.3.6.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: ru-RU (ru_RU.UTF-8); UI: ru-RU
Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.1
Calc: threaded
Comment 3 Marcool 2022-10-04 15:13:49 UTC
I am not able to reproduce in 7.3.6.2 either, which is the "still" version, as the archlinux package is called, as opposed to the "fresh" which is at 7.4.1.3 now, and was at 7.4.0.3 when I posted this report.
Comment 4 Roman Kuznetsov 2022-10-04 15:40:35 UTC
Ok, still no repro even in current dev version

Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: 55ee3ede2bb0211e895053ed3a54bb1c99cc94ca
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: ru-RU (ru_RU.UTF-8); UI: en-US
Calc: threaded

Do you use Wayland may be?
Comment 5 Marcool 2022-10-04 15:54:40 UTC
No Wayland no, X11:

Operating System: Arch Linux
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.12-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20L6S8FB00
System Version: ThinkPad T480
Comment 6 Michael Weghorn 2022-10-11 13:18:33 UTC
Can't reproduce on Debian testing with

Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: a0bc0cc81b597aa81189355a8125753d6b873cce
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

Does this happen with any newly created document and any text?
Is it also reproducible when you save the document and reopen instead of creating a new document? If so, please attach a sample document.

Can you try whether this also happens if you start LibreOffice with environment variable SAL_USE_VCLPLUGIN=gtk3 or SAL_USE_VCLPLUGIN=gtk3 set? (Please also copy the information from "Help" -> "About LibreOffice" you get for these cases).

What would also be helpful is to know whether this still happens when you try with a current daily build. If you want to try this, instructions for this are available here:
https://wiki.documentfoundation.org/QA/Testing_Daily_Builds
Comment 7 Marcool 2022-10-29 18:27:21 UTC
Hi Michael, hi all

Sorry it took me a while to get back to this, been busy at work, and sick, and busy again...

I just installed the latest dev build, 7.5.0.0.alpha0 from here: https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@tb87-TDF/current/ via a PKGBUILD derived from this one: https://aur.archlinux.org/packages/libreoffice-dev-bin and using a clean profile and...

I can't reproduce the glitch in that context.

I actually can't reproduce it at all now, not even in the "fresh" branch and using my own profile.

Maybe I just had a non-LO related graphical issue on my system - possibly something relating to font rendering? - that has been fixed by an update to some other component?

In any case thank you for looking into the report, and my apologies for wasting your time if this does turn out to just be a one-off fluke of my setup.

Best,
Mark.
Comment 8 Michael Weghorn 2022-10-30 15:40:30 UTC
(In reply to Marcool from comment #7)
> In any case thank you for looking into the report, and my apologies for
> wasting your time if this does turn out to just be a one-off fluke of my
> setup.

Hi Mark, thanks a lot for double-checking!
Good to hear it's working as expected now.

And don't worry, you're not at all wasting our time. Writing good bug reports that contain all relevant information - like this one - is a very valuable thing, so thanks for doing it! And it's a thing that happens from time to time that something sometimes behaves differently for some unknown reason...
Comment 9 Marcool 2022-10-31 08:45:41 UTC
Thanks for your kind comment Michael. Glad to (try to) help.
Best.
Mark