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

            Bug ID: 152012
           Summary: Assertion failure on opening date picker
           Product: LibreOffice
           Version: 7.5.0.0 alpha0+ Master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 183551
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183551&action=edit
Date picker

Description:
While opening the date picker from a DOCX document, I get assertion failure


Steps to Reproduce:
1. Open DOCX attachment
2. Try opening the date picker by clicking on the down button


Actual Results:
Assertion Failure


Expected Results:
No assertion failure


Reproducible: Always


User Profile Reset: No


Additional Info:
The problem does not happen with GTK3 UI. It happened both with X11, GTK4 and
Windows UI.

The problem happens in the latest LO 7.5 dev:

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ab4e40941e9ebae83f98ba918440b03eac5bdcaa
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3c0be5564afe1b9cc843a49aba88b72af74c43ab
CPU threads: 32; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_DE); UI: en-US
Calc: threaded

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ab4e40941e9ebae83f98ba918440b03eac5bdcaa
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk4
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

The problem does not happen with GTK3 UI:

Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ab4e40941e9ebae83f98ba918440b03eac5bdcaa
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

Reply via email to