Bug 169285 - Toolbar text and icons are invisible except in safe mode
Summary: Toolbar text and icons are invisible except in safe mode
Status: RESOLVED DUPLICATE of bug 166803
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.8.2.2 release
Hardware: ARM Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: QA:needsComment
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-06 04:30 UTC by David Martin
Modified: 2026-01-22 12:53 UTC (History)
1 user (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 David Martin 2025-11-06 04:30:11 UTC
Description:
I tried light and dark themes. I tried different icons like colibre, breeze etc. I tried with force skia software rendering on. Nothing works. Safe mode shows up fine but I can't just always use safe mode.
This is a new laptop with a new installation of LibreOffice, using all default settings. ARM version on Windows 11 with Snapdragon CPU.

Steps to Reproduce:
1. Turn computer on
2. Open literally any document or just create a new one.
3. Boom, it shows no text or icons in the toolbars

Actual Results:
Toolbar text and icons are invisible.

Expected Results:
Toolbars should be visible and thus functional.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 David Martin 2025-11-06 18:47:04 UTC
Please note I learned of a fix. If I disable 'use anti aliasing' and 'use skia' so that I have access to the hardware rendering option, I selected hardware rendering and was subsequently able to see toolbars and icons correctly. I was able to enable anti aliasing afterwards too. I just can't use Skia
Comment 2 Christian Lohmaier 2026-01-22 12:53:33 UTC
looks like a cross-compilation issue

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