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

            Bug ID: 166108
           Summary: Erroneous notification of "Default file formats not
                    registered" when they are.
           Product: LibreOffice
           Version: 24.8.5.2 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
On every start of LO Writer I get a popup claiming .odt is not registered as
the default to be opened by LO.

It IS, in both windows 11 and LO.

Steps to Reproduce:
1.open libreoffice writer - that's all. And pop-up notification appears.
2.
3.

Actual Results:
Write opens to a new blank document then the pop-up notification appears on
top, front and center:
pop-up title bar: Default file formats not registered
Notification content:
 " The following file formats are not registered to be opened by default in
LibreOffice: .odt 
Select OK if you want to change default file format registrations."

I have this option selected:
[x] Perform check on startup

Expected Results:
I expect LO to perform the check, but when it confirms that .odt IS registered
in both Win11 and LO to be opened by default by LO Writer in this case, there
should be no pop-up Notification claiming erroneously that it is not
registered.
There should be no notification at all in this case.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes

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

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

Reply via email to