Bug 43563 - : Libreoffice crashes in KDE 4.7.2 (kubuntu 11.10) when Polyster style is enabled
Summary: : Libreoffice crashes in KDE 4.7.2 (kubuntu 11.10) when Polyster style is ena...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
3.4.4 release
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Luboš Luňák
Whiteboard: BSA
Depends on:
Reported: 2011-12-06 18:30 UTC by kamesh
Modified: 2013-11-27 14:06 UTC (History)
0 users

See Also:
Crash report or crash signature:
Regression By:

Strace (370.38 KB, application/bzip2)
2011-12-06 18:30 UTC, kamesh
Backtrace (17.90 KB, text/plain)
2012-01-14 13:35 UTC, kamesh

Note You need to log in before you can comment on or make changes to this bug.
Description kamesh 2011-12-06 18:30:05 UTC
Created attachment 54167 [details]

Problem description:

Libreoffice (all components including writer, spreadsheet, impress etc.) crashes in KDE4.7.2 (kubuntu 11.10) when Polyster style is enabled. With the default oxygen style it does not crash.

Steps to reproduce:
1. Enable Polyster style. May have to use package manager to install. 
2. Open Libreoffice writer
3. It crashes

Current behavior: It crashes

Expected behavior: It should not crash.

Platform (if different from the browser): Kubuntu 11.10. KDE 4.7.2. 3.0.0-13-generic-pae kernel. 
Browser: Opera/9.80 (X11; Linux i686; U; en) Presto/2.10.229 Version/11.60
Comment 1 Luboš Luňák 2012-01-05 08:27:46 UTC
Strace is usually useless for crashes. Please provide a backtrace from the crash (http://wiki.documentfoundation.org/BugReport#How_to_get_backtrace_.28on_Linux.29).
Comment 2 kamesh 2012-01-14 13:35:08 UTC
Created attachment 55584 [details]

As requested, backtrace is attached. Thanks.
Comment 3 Luboš Luňák 2012-01-16 08:55:37 UTC
The bug is in the style. Function PolyesterStyle::drawComplexControl() dereferences the widget pointer argument in the CC_ToolButton case even though Qt documentation says the argument is optional and can therefore be NULL. You'll need to report to the style developers.