Bug 358728

Summary:	Crash when opening the Fonts KCM (QRasterPaintEngine::renderHintsChanged)
Product:	[Applications] systemsettings	Reporter:	Willem <willemsonke>
Component:	kcm_fontinst	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	wbauer1
Priority:	NOR
Version:	5.5.3
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Garbled font rendering in the Font Management KCM

Description Willem 2016-01-29 10:06:49 UTC

When I try to launch the Font Management KCM from the System Settings, the application crashes. This happens every time I try.

Reproducible: Always

Steps to Reproduce:
1. From the main windows of the System Settings, select Font.
2. In the left sidebar, click Font Management.

Actual Results:  
The software crashes with the backtrace pasted here: https://paste.kde.org/p2nqfazrg

Expected Results:  
Show the Font Management KCM and not crash ;)

Application: systemsettings5 (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

I'm using the kubuntu-ppa/backports PPA.

If I launch the Font Management module separately using KRunner, the application does not crash. However, the font preview is garbled, which might be related? See the attached screenshot.

Comment 1 Willem 2016-01-29 10:08:05 UTC

Created attachment 96900 [details]
Garbled font rendering in the Font Management KCM

Comment 2 Wolfgang Bauer 2016-01-29 10:37:18 UTC

FYI, the garbled font rendering should be fixed in 5.5.4.
See Bug#336089.

No idea if that would also fix your crash though.

Comment 3 Willem 2016-03-01 14:59:16 UTC

I just received the upgrade to 5.5.4 and the crash does not occur anymore. So I assume it was related to the garbled font rendering (which is, indeed, also fixed now). Thanks!

Comment 4 Wolfgang Bauer 2016-03-07 20:37:58 UTC

(In reply to Willem from comment #3)
> I just received the upgrade to 5.5.4 and the crash does not occur anymore.
> So I assume it was related to the garbled font rendering (which is, indeed,
> also fixed now). Thanks!

Thank you for confirming. :-)
I'll mark this as duplicate then (though it probably doesn't matter really... ;-) ).

*** This bug has been marked as a duplicate of bug 336089 ***