Bug 144875 - artefacts in UI
Summary: artefacts in UI
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.1.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-02 14:17 UTC by zenon49
Modified: 2022-05-02 03:37 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
artefacts in UI (117.06 KB, image/png)
2021-10-02 14:17 UTC, zenon49
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zenon49 2021-10-02 14:17:04 UTC
Created attachment 175458 [details]
artefacts in UI

With time artefacts in UI increase, see picture. When I do a mouseover on an UI element it disappears for a short time. It can been observed in all libreoffice applications.
Comment 1 V Stuart Foote 2021-10-02 20:19:43 UTC
Sounds/looks like a Skia Vulkan rendering issue.

Please post your skia.log and the Help -> About LibreOffice panel details.

Do "artifacts" clear if you disable Skia Vulkan and work in Skia software raster rendering or without Skia using just default GDI rendering?
Comment 2 QA Administrators 2022-04-01 03:40:17 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2022-05-02 03:37:26 UTC
Dear zenon49,

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-FollowUp