Bug 162817 - LibreOffice kf6 is extremely laggy while scrolling when fractional scaling is enabled
Summary: LibreOffice kf6 is extremely laggy while scrolling when fractional scaling is...
Status: RESOLVED DUPLICATE of bug 152911
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
24.8.0.3 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Qt6
  Show dependency tree / graph
 
Reported: 2024-09-05 21:00 UTC by pasta-grandpa-lard
Modified: 2024-09-09 06:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description pasta-grandpa-lard 2024-09-05 21:00:29 UTC 
Description:
On a KDE Plasma system (openSUSE Tumbleweed), scrolling through a document in LibreOffice Writer is extremely laggy and runs at a very low frame rate when fractional scaling is enabled.

Steps to Reproduce:
1. Scale a KDE Plasma session up to 150%
2. Open LibreOffice Writer
3. Scroll through a multi-page document

Actual Results:
The document scrolls, but it is extremely laggy

Expected Results:
The document scrolls smoothly as it does while running under X11


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.8.0.3 (X86_64) / LibreOffice Community
Build ID: 480(Build:3)
CPU threads: 16; OS: Linux 6.10; UI render: default; VCL: kf6 (cairo+wayland)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Rafael Lima 2024-09-06 17:44:03 UTC 
I get a very choppy scrolling with the mouse when there are images/objects in the Writer documents.

When it's only text, scrolling is good.

On X11 no issues... so it seems to be a Wayland + kf6 thing.

@Michael, do you experience this as well?
Comment 2 Michael Weghorn 2024-09-09 06:49:44 UTC 
(In reply to Rafael Lima from comment #1)
> @Michael, do you experience this as well?

This sounds like the issue tracked in tdf#152911, see tdf#152911 comment 13 for a first analysis.

*** This bug has been marked as a duplicate of bug 152911 ***