Description of problem: *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Version-Release number of selected component (if applicable): 7.0.2.2 How reproducible: using macros in the libreoffice calc Steps to Reproduce: 1. start the libreoffice calc 2. run the macros 3. Actual results: It seems to work and not crashing, but there is a lot of debug messages from the libreoffice calc. Expected results: - no debug messages come out Additional info: [jari@ENVY-17 GDS]$ soffice ./dr_waiver_list_LVDS_TOP_V1.xls State is 0 State is 0 State is 0 State is 0 *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug
With all document, or just some specific ones ? Is desktop scaling enabled, and if it is what % is it ?
I'm guessing it is 'fixed' in this later installed version: [jari@ENVY-17 ample]$ soffice --version LibreOffice 6.4.7.2 40(Build:2) It didn't appear anymore.
Original report was LibreOffice 7.0.2.2 on Fedora 33, comment #2 though is LibreOffice 6.4.7.2 which would be Fedora 32. So I don't know if the problem persists in Fedora 33 with current LibreOffice 7.0.4.2 ?
Thats correct. The problem didn't appear with 6.4.x, but with 7.0.x I still get below message on the terminal: [jari@ENVY-17 c_code]$ soffice State is 0 State is 0 State is 0 . . .
The "State is 0" lines are coming from LibreOffice itself as some overlooked debugging line: upstreamed fix as https://gerrit.libreoffice.org/c/core/+/109482 I don't see the other messages, those are presumably from pixman.
we'll have the fix what I see in the next upstream release