Bug 157494 - Track-pad scrolling in Flatpak Writer is slow and laggy.
Summary: Track-pad scrolling in Flatpak Writer is slow and laggy.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.2.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-28 15:33 UTC by n1729
Modified: 2024-05-11 03:16 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description n1729 2023-09-28 15:33:19 UTC
Description:
Scrolling using track-pad on writer is not fluid and feels laggy. Comparing with scrolling on Firefox and only-office where scrolling is smooth.

Troubleshooting tried:
1. Scrolling performance on Native distro version is same as flatpak version.
2. Turned on smooth scrolling option without any effect.

Is there any other information which I can share which will be helpful?

System Information:
DE: KDE Plasma 5.27.8 [Wayland]
Distro: openSUSE Tumbleweed
Display:2560x1440 [150% scale]
Refresh rate: 165 hz
Laptop: Asus ROG Strix G513QY

Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-IN (en_DK.UTF-8); UI: en-US
Flatpak
Calc: threaded

Steps to Reproduce:
1. Open .docx word file.
2. Scroll using two fingers(fast or slow) on touch-pad [Native-scrolling turned on].
3. Document scrolling feels laggy.

Actual Results:
Scrolling is not smooth on 165 Hz display on 150 % fractional scaling.

Expected Results:
Scrolling should be smooth on Wayland with 165 Hz refresh rate.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-IN (en_DK.UTF-8); UI: en-US
Flatpak
Calc: threaded

Launching from Terminal:

flatpak run org.libreoffice.LibreOffice
Failed to open display

(soffice:41): Gtk-WARNING **: 21:02:30.611: Locale not supported by C library.
        Using the fallback 'C' locale.
Comment 1 Buovjaga 2023-10-11 10:59:44 UTC
(In reply to n1729 from comment #0)
> Description:
> Scrolling using track-pad on writer is not fluid and feels laggy. Comparing
> with scrolling on Firefox and only-office where scrolling is smooth.
> 
> Troubleshooting tried:
> 1. Scrolling performance on Native distro version is same as flatpak version.
> 2. Turned on smooth scrolling option without any effect.

If the performance is the same on non-Flatpak version, do we need to mention Flatpak in the summary? Flatpak-only bugs should be reported to https://github.com/flathub/org.libreoffice.LibreOffice/issues

There is bug 98181 for glitchy touchpad scrolling on Linux
Comment 2 Stéphane Guillou (stragu) 2023-10-12 20:29:38 UTC
Given the fairly high resolution, I'm wondering if bug 154602 is a better fit.
Does the lag also happen on other scrolling methods, like using arrows or page down?
Comment 3 QA Administrators 2024-04-10 03:13:25 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2024-05-11 03:16:58 UTC
Dear n1729,

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