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

            Bug ID: 167767
           Summary: CMIS connection failure and crash with Alfresco 5.1.0
                    on LibreOffice 25.x (works on 7.6.7)
           Product: LibreOffice
           Version: 25.2.5.2 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
LibreOffice 25.2.5.2 fails to open remote documents from an Alfresco 5.1.0
server via the CMIS protocol.
The same procedure works flawlessly in LibreOffice 7.6.7.
The issue is reproducible on both Windows and Linux, affecting all users.
The Alfresco server uses CMIS API version 1.1.

Steps to Reproduce:
>From a web portal, click a link generated with the vnd.libreoffice.cmis://
protocol pointing to a document hosted on an Alfresco 5.1.0 server.
Example (sanitized):

perl
Copiar
Editar
vnd.libreoffice.cmis://http%3A%2F%2Fexample.com%2Falfresco%2Fapi%2F-default-%2Fpublic%2Fcmis%2Fversions%2F1.1%2Fatom%23-default-/document.odt

Alternatively, execute a terminal command opening LibreOffice with the encoded
CMIS URL above.

Actual Results:
With HTTPS: LibreOffice crashes immediately.

gdbtrace.log shows a Segmentation fault during request dispatch, indicating a
possible null pointer dereference in the CMIS connection code.

With HTTP: LibreOffice does not crash but fails to open the document, showing a
"Document Recovery" dialog.

Expected Results:
The document opens normally in LibreOffice for editing.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Works in: 7.6.7

Fails in: 25.2.5.2

Testing intermediate versions is in progress to narrow down the exact
regression point.

Environment:

LibreOffice 25.2.5.2
Alfresco Community 5.1.0 (CMIS 1.1)
OS: Windows 10 x64, Ubuntu 22.04 LTS x64 (both affected

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

Reply via email to