Bug 166803 - No icons show in the UI AARM64 Win64 builds with skia lib rendering (neither raster nor Vulkan), GDI+ works but slow (comment 22 for workaround)
Summary: No icons show in the UI AARM64 Win64 builds with skia lib rendering (neither ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.2.3.2 release
Hardware: ARM Windows (All)
: highest normal
Assignee: Not Assigned
URL: https://ask.libreoffice.org/t/the-ico...
Whiteboard: needsWin64ARM target:25.8.5
Keywords:
: 166819 167294 167612 168060 168338 168345 168549 169187 169285 169538 169635 170296 (view as bug list)
Depends on:
Blocks: Skia 164970
  Show dependency treegraph
 
Reported: 2025-05-31 08:03 UTC by Kihan
Modified: 2026-01-23 11:42 UTC (History)
24 users (show)

See Also:
Crash report or crash signature:


Attachments
Light theme no icons (118.11 KB, image/png)
2025-06-02 06:53 UTC, alex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kihan 2025-05-31 08:03:22 UTC
Description:
My Libre Office is AARCH64 25.2.3.2 on Windows 11 ARM

When I launch the Libre Office, there is no icon in tool bar.
I tried to change the icon theme, appearance from dark to light, language from Korean to English(US).
I removed and installed several times.
However it was same.

Steps to Reproduce:
1.Launch Libre office
2.Create a file or open a file of Impress, Clac, Writer and Base

Actual Results:
The icons looks like blanks

Expected Results:
The Icons shows in tool bars.


Reproducible: Always


User Profile Reset: No

Additional Info:
I asked it on ask.libreoffice.com like below

https://ask.libreoffice.org/t/the-icons-are-not-appeared/122667
Comment 1 V Stuart Foote 2025-05-31 13:35:11 UTC Comment hidden (obsolete)
Comment 2 V Stuart Foote 2025-05-31 14:50:25 UTC Comment hidden (obsolete)
Comment 3 Mike Kaganski 2025-05-31 14:56:03 UTC Comment hidden (obsolete)
Comment 4 V Stuart Foote 2025-05-31 15:47:05 UTC Comment hidden (obsolete)
Comment 5 V Stuart Foote 2025-05-31 15:59:53 UTC Comment hidden (obsolete)
Comment 6 V Stuart Foote 2025-06-02 06:23:12 UTC
*** Bug 166819 has been marked as a duplicate of this bug. ***
Comment 7 V Stuart Foote 2025-06-02 06:23:52 UTC Comment hidden (obsolete)
Comment 8 alex 2025-06-02 06:35:52 UTC
Adding comments from my (dupe) 166819:
-Changing icon theme doesn't fix.
-Light/Dark mode no difference.
-Totally new profile no difference.

Disabling Skia fixes ok.

Happy to do any further testing or provide further info to help.
Comment 9 alex 2025-06-02 06:51:43 UTC Comment hidden (obsolete)
Comment 10 alex 2025-06-02 06:53:38 UTC Comment hidden (obsolete)
Comment 11 alex 2025-06-02 06:59:29 UTC
Further Skia.log below with 'Force Skia Software Rendering' -still no icons.
(From my dupe, unchecking 'Use Skia for all rendering' allows icons to appear, but seems much slower in use. 

RenderMethod: raster
Compiler: Clang
Comment 12 V Stuart Foote 2025-06-02 14:26:47 UTC Comment hidden (obsolete)
Comment 13 V Stuart Foote 2025-06-21 00:12:21 UTC
*** Bug 167129 has been marked as a duplicate of this bug. ***
Comment 14 V Stuart Foote 2025-06-30 14:43:01 UTC
*** Bug 167294 has been marked as a duplicate of this bug. ***
Comment 15 radek.reif 2025-08-20 19:34:31 UTC Comment hidden (obsolete)
Comment 16 mike7496+bgz 2025-08-26 00:29:46 UTC Comment hidden (obsolete)
Comment 17 Yuri Litvinenko 2025-08-26 00:31:57 UTC Comment hidden (obsolete)
Comment 18 si458 2025-08-27 10:42:56 UTC Comment hidden (obsolete)
Comment 19 m_a_riosv 2025-09-25 21:03:15 UTC
*** Bug 168549 has been marked as a duplicate of this bug. ***
Comment 20 João Gomes 2025-09-30 18:44:48 UTC Comment hidden (obsolete)
Comment 21 alex 2025-09-30 20:12:22 UTC
If it's of any assistance, yesterday I got frustrated with the slow non-skia performance and went through the process of reinstalling old versions until before this issue was introduced.

I have ended up running 25.2.1.1 (installed from https://downloadarchive.documentfoundation.org/libreoffice/old/25.2.1.1/win/aarch64/) which has resolved the issue for now, but is far from ideal.

I understand that ARM hardware is less common for the userbase and possibly not available to developers, but the present circumstance makes Libreoffice look like a broken product to users of brand-new Windows hardware.

I am very happy to help testing builds that try to resolve this, as I'm sure others in the thread will be.
Thanks!
Comment 22 Leandro Cerencio 2025-10-28 23:12:34 UTC
I discovered one solution. I dont know if it is reproducible but

1. Go to Tools -> Options
2. In View Section, turn off "Use anti-aliasing" and "Use Skia"
3. It will allow "Use hardware acceleration", turn on.
4. It should restart Libreoffice with visible icons.
5. Go back to View Section and turn on "Use anti-aliasing" and "Use Skia"

It should appear icons on toolbar.

Tested on 25.8.2.2 version from scoop.sh.
Comment 23 Leandro Cerencio 2025-10-28 23:15:50 UTC
(In reply to Leandro Cerencio from comment #22)
> I discovered one solution. I dont know if it is reproducible but
> 
> 1. Go to Tools -> Options
> 2. In View Section, turn off "Use anti-aliasing" and "Use Skia"
> 3. It will allow "Use hardware acceleration", turn on.
> 4. It should restart Libreoffice with visible icons.
> 5. Go back to View Section and turn on "Use anti-aliasing" and "Use Skia"
> 
> It should appear icons on toolbar.
> 
> Tested on 25.8.2.2 version from scoop.sh.

5. it is wrong. You cant turn on "Use Skia"
Comment 24 V Stuart Foote 2025-11-01 14:23:54 UTC
*** Bug 169187 has been marked as a duplicate of this bug. ***
Comment 25 Herbert Weis 2025-11-01 19:24:55 UTC
Thank you, Leandro, for comment #22. It works perfectly, thank you very much!

Best regards, Herbert
Comment 26 Hmasteen 2025-11-06 10:25:29 UTC
Hi,

It looks like I'm having the same bug.

The workaround worked for me.

Here is my setup:

Version: 25.8.2.2 (AARCH64)
Build ID: d401f2107ccab8f924a8e2df40f573aab7605b6f
CPU threads: 12; OS: Windows 11 ARM64 (build 26200); UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 27 V Stuart Foote 2025-11-19 19:23:29 UTC
*** Bug 168345 has been marked as a duplicate of this bug. ***
Comment 28 V Stuart Foote 2025-11-19 19:23:55 UTC
*** Bug 169538 has been marked as a duplicate of this bug. ***
Comment 29 V Stuart Foote 2025-11-23 17:40:06 UTC
*** Bug 169635 has been marked as a duplicate of this bug. ***
Comment 30 m.wedler 2025-11-23 19:37:29 UTC
The work around also works for me.
Comment 31 Volodymyr 2025-11-27 21:51:34 UTC Comment hidden (obsolete)
Comment 32 m.wedler 2025-11-28 05:46:50 UTC Comment hidden (obsolete)
Comment 33 juli gain 2025-12-17 11:19:06 UTC Comment hidden (spam)
Comment 34 stefan.seeland 2026-01-01 13:18:23 UTC
*** Bug 167612 has been marked as a duplicate of this bug. ***
Comment 35 Felix B. 2026-01-02 06:27:30 UTC
I can hereby confirm that the workaround works fine on my Lenovo ThinkPad T14s G6 with ARM Snapdragon (Windows 11 Pro ARM).
Comment 36 m_a_riosv 2026-01-12 00:37:51 UTC
*** Bug 170296 has been marked as a duplicate of this bug. ***
Comment 37 Christian Lohmaier 2026-01-22 12:45:38 UTC
*** Bug 168060 has been marked as a duplicate of this bug. ***
Comment 38 Christian Lohmaier 2026-01-22 12:46:35 UTC
*** Bug 168338 has been marked as a duplicate of this bug. ***
Comment 39 Christian Lohmaier 2026-01-22 12:53:33 UTC
*** Bug 169285 has been marked as a duplicate of this bug. ***
Comment 40 Commit Notification 2026-01-23 11:38:25 UTC
Christian Lohmaier committed a patch related to this issue.
It has been pushed to "libreoffice-25-8":

https://git.libreoffice.org/core/commit/fb26dc53132bdd298b323d81f030f27884a4e363

tdf#166803 – wsl-as-helper: fix cross-compilation to aarch64

It will be available in 25.8.5.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 41 Christian Lohmaier 2026-01-23 11:42:13 UTC
(the problem is not actually the cross-compilation, that's just a fix to allow building on the new baseline, the culprit is actually Visual Studio - compile with Visual Studio 2019 → bug, compile with Visual Studio 2022 → OK. Visual Studio 2022 cannot be installed on old baseline, so builds for win/aarch64 have to be done on new baseline to address this issue)