kcmshell5 crashed with SIGSEGV in XAddExtension()

Bug #1780145 reported by Bruno Lopes da Silva on 2018-07-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde-cli-tools (Ubuntu)

Bug Description

KDE Settings freezes when you open "Fonts Management"

Dist.: Kubuntu Cosmic 18.10 Daily

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: kde-cli-tools 4:5.12.6-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Jul 4 13:20:47 2018
ExecutablePath: /usr/bin/kcmshell5
InstallationDate: Installed on 2018-07-03 (0 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180702)
ProcCmdline: /usr/bin/kcmshell5 fontinst
 PATH=(custom, no user)
Signal: 11
SourcePackage: kde-cli-tools
 XAddExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libXft.so.2
 XftDefaultHasRender () from /usr/lib/x86_64-linux-gnu/libXft.so.2
 XftDefaultSubstitute () from /usr/lib/x86_64-linux-gnu/libXft.so.2
 XftFontMatch () from /usr/lib/x86_64-linux-gnu/libXft.so.2
Title: kcmshell5 crashed with SIGSEGV in XAddExtension()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

information type: Private → Public

 XAddExtension (dpy=dpy@entry=0x563c0947de30) at ../../src/InitExt.c:73
 _XftDisplayInfoGet (dpy=0x563c0947de30, createIfNecessary=<optimized out>) at ../../src/xftdpy.c:91
 XftDefaultHasRender (dpy=dpy@entry=0x563c0947de30) at ../../src/xftdpy.c:254
 XftDefaultSubstitute (dpy=dpy@entry=0x563c0947de30, screen=screen@entry=0, pattern=pattern@entry=0x563c09981c00) at ../../src/xftdpy.c:462
 XftFontMatch (dpy=dpy@entry=0x563c0947de30, screen=screen@entry=0, pattern=pattern@entry=0x563c09981be0, result=result@entry=0x7fff7086b34c) at ../../src/xftfont.c:52

Changed in kde-cli-tools (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

I reproduced the bug. It's atached.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers