https://bugs.documentfoundation.org/show_bug.cgi?id=172985

            Bug ID: 172985
           Summary: Calc grid lines rendered with inconsistent thickness
                    using Qt6/KF6 backend on Wayland
           Product: LibreOffice
           Version: 26.2.5.2 release
          Hardware: x86 (IA32)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Description:
The grid lines in LibreOffice Calc are rendered incorrectly when using the
Qt6/KF6 VCL backend on a Wayland session.
Horizontal grid lines are displayed with inconsistent thickness, and some
vertical grid lines appear dashed or uneven.
This only affects the visual grid lines. Cell borders are rendered correctly,
and the issue does not affect printing or exported documents.
The problem is reproducible with a new, empty spreadsheet.

Steps to Reproduce:
1. Start LibreOffice Calc.
2. Create a new empty spreadsheet.
3. Observe the default grid lines.

Actual Results:
Grid lines are rendered inconsistently.
- Horizontal grid lines have alternating thickness.
- Some vertical grid lines appear dashed or partially missing.
- The appearance is independent of the zoom level (tested at 100%, 120%, and
200%).

Expected Results:
All grid lines should be rendered uniformly with consistent thickness.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
The issue appears to be specific to the Qt6/KF6 backend under Wayland.

The problem disappears completely when using either:

- SAL_USE_VCLPLUGIN=gtk3
- QT_QPA_PLATFORM=xcb (XWayland)

The issue is still present when explicitly forcing:

- SAL_USE_VCLPLUGIN=qt6
- SAL_USE_VCLPLUGIN=kf6

Disabling hardware acceleration does not change the behaviour.

The issue affects only the visual rendering of Calc grid lines.
Cell borders, printing and document contents are unaffected.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to