Bug 167045 - Post-update, Windows 11 tray icon for LibreOffice Writer does not show list upon right-click
Summary: Post-update, Windows 11 tray icon for LibreOffice Writer does not show list u...
Status: RESOLVED DUPLICATE of bug 76131
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
25.2.4.3 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-16 12:05 UTC by mlmckinney1984
Modified: 2025-06-16 13:28 UTC (History)
1 user (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 mlmckinney1984 2025-06-16 12:05:21 UTC 
Description:
As the title says, when I click my tray icon for Writer now it no longer shows a list of recently opened docs and docs pinned to that list. 

Steps to Reproduce:
1. Pin program to task bar
2. Right-click


Actual Results:
Nothing

Expected Results:
1. Pin program to task bar
2. Right-click
3. Dialog box pops up with list of recent docs and pinned items


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 25.2.4.3 (X86_64) / LibreOffice Community
Build ID: 33e196637044ead23f5c3226cde09b47731f7e27
CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 1 V Stuart Foote 2025-06-16 13:28:02 UTC 
Can not confirm. The Windows Jump list entries are intact.

This would be an issue on update from prior release, e.g. 24.8.x -> 25.2.x bug 76131, but has not been an issue with the monthly incremental updates (MAR or MSI based).

Version: 25.2.4.3 (X86_64) / LibreOffice Community
Build ID: 33e196637044ead23f5c3226cde09b47731f7e27
CPU threads: 8; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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