Bug 126664 - Crash on start: QPaintDevice: Cannot destroy paint device that is being painted
Summary: Crash on start: QPaintDevice: Cannot destroy paint device that is being painted
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.5.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: corruptProfile
Depends on:
Blocks:
 
Reported: 2019-08-01 17:50 UTC by rwman
Modified: 2019-09-03 08:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rwman 2019-08-01 17:50:13 UTC
Description:
I have found a workaround, creteing this bug for reference.

When i start libreoffice, it displays recovery dialog, then i click discard, then libreofice crashes with error:
QPaintDevice: Cannot destroy paint device that is being painted

After i have renamed my ~/.config/libreoffice/ dir, the bug is gone.

Steps to Reproduce:
1. start Libreoffice

Actual Results:
It crashed

Expected Results:
It should start


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
os: openSUSE tumbleweed linux
distribution method: openSUSE rpms
desktop: KDE5

> glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile 
OpenGL core profile version string: 4.2 (Core Profile) Mesa 19.1.3
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 19.1.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.1.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:


same bug on arch linux: https://bbs.archlinux.org/viewtopic.php?id=245072
same bug on manjaro linux: https://forum.openoffice.org/en/forum/viewtopic.php?f=49&t=97761
Comment 1 Julien Nabet 2019-08-02 06:49:50 UTC
If you don't reproduce this after having renamed your LO directory profile, it could mean the bug has been fixed or something was corrupted in LO profile.

If you can't reproduce the bug now, I'd put RESOLVED/WFM.
Comment 2 Xisco Faulí 2019-09-03 08:19:21 UTC
Indeed, it seems like a corrupted profile issue.
Closing as RESOLVED WORKSFORME