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

            Bug ID: 157935
           Summary: After installation of 7.6.2, first form opening of
                    .odb file freezes LO
           Product: LibreOffice
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: macOS (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Installation
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: w...@sorha-consulting.be

Created attachment 190440
  --> https://bugs.documentfoundation.org/attachment.cgi?id=190440&action=edit
"LibreOffice" folder (created with LO 7.6.2)

System:
MacBook Pro (Retina, 13-inch, Early 2015)
MacOS 12.7 (Monterey)

After installation of LO 7.6.2, I open an .odb (Base) file.
A "LibreOffice" folder is created within /users/XXX/Library/Application Support
This folder includes a folder named "4" which includes 2 folders : "cache" &
"user" (which is the user profile, I suppose)
This .odb file has a startup macro displaying a pop-up with user/pwd fields.
This macro works well (login is properly checked) and access is allowed to the
database.
A second macro, immediately following the login, displays a form with several
buttons.

Here is the bug: the form is displayed but remains blank (no button) and LO
freezes.

Workaround (and possibly a source to look at to solve the problem):
Uninstall LO 7.6.2
Delete the folder /users/Library/Application Support/Libreoffice/4
Install an older version of LO (I've tried LO 7.1.4.1)
Open it (it creates a "/users/Library/Application Support/Libreoffice/4" file)
Open the .odb file.
It works (form is well displayed and all buttons are functional)
Quit LO
Install LO 7.6.2
Open it, open the .odb file. It works !

First guess: LO 7.6.2 creates a corrupted profile. When the profile already
exists (not corrupted), it uses it and it works

Attachments: both profiles (created with LO 7.1.4.1 & 7.6.2)

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

Reply via email to