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

V Stuart Foote <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected],
                   |                            |[email protected]
             Status|UNCONFIRMED                 |NEEDINFO
     Ever confirmed|0                           |1

--- Comment #1 from V Stuart Foote <[email protected]> ---
Can not confirm.

Version: 24.8.4.2 (X86_64) / LibreOffice Community
Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002
CPU threads: 8; OS: Windows 10 X86_64 (10.0 build 19045); UI render:
Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded


Could be something new with the Win11 (24H2) release build you're on.

This loss of file association (e.g. scalc.exe not associated with .ods ODF
spreadsheet, and soffice.exe instead) should not happen, but we have seen past
instances on Windows os/DE when MS Office product install has corrupted the
registration of the soffice.bin associated .exe wrapper programs.

Use the os/DE file association manager, LibreOffice provides a launcher from
its Tools -> Options -> General 'Windows Default Apps' button.

Find the LibreOffice listed in the dialog, and use its 'Manage' button.

You'll see the MS API provided handling of "File type and protocol
associations" as currently registered on your system.

If you like you could try to fully uninstall LibreOffice, clean the windows
registry of any LibreOffice associations and rename or delete any of the
LibreOffice user profiles. And then reinstall clean from the MSI package.

Let us know if after the clean install you still are missing file associations
in the either the Win11 "File Explorer" and in the Win11: Settings ->  Default
Apps -> Set defaults by app  reviewing the LibreOffice "File type and Protocol
associations".

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

Reply via email to