apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]

Bug #1552577 reported by Pavel Zlámal on 2016-03-03
This bug affects 42 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
gtk+3.0 (Ubuntu)

Bug Description


Crash displayed after logging in.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: apport-gtk 2.20-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 1 22:13:24 2016
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2016-02-21 (10 days ago)
InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
 Segfault happened at: 0x7f3a0219cb89: mov (%rbx),%rdi
 PC (0x7f3a0219cb89) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)

Pavel Zlámal (zlamal-pavel) wrote :

 _gtk_style_provider_private_get_settings (provider=0x0) at /build/gtk+3.0-qjgeoX/gtk+3.0-3.18.8/./gtk/gtkstyleproviderprivate.c:123
 gtk_css_value_initial_compute (value=<optimized out>, property_id=1, provider=0x0, style=0x194fd60, parent_style=0x0) at /build/gtk+3.0-qjgeoX/gtk+3.0-3.18.8/./gtk/gtkcssinitialvalue.c:52
 gtk_css_static_style_compute_value (style=0x194fd60, provider=0x0, parent_style=0x0, id=1, specified=0x7f3a02809cd0 <inherit>, section=0x0) at /build/gtk+3.0-qjgeoX/gtk+3.0-3.18.8/./gtk/gtkcssstaticstyle.c:232
 _gtk_css_lookup_resolve (lookup=lookup@entry=0x1961170, provider=provider@entry=0x0, style=style@entry=0x194fd60, parent_style=parent_style@entry=0x0) at /build/gtk+3.0-qjgeoX/gtk+3.0-3.18.8/./gtk/gtkcsslookup.c:125
 gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at /build/gtk+3.0-qjgeoX/gtk+3.0-3.18.8/./gtk/gtkcssstaticstyle.c:191

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
tags: added: yakkety
tags: added: zesty
information type: Private → Public
Mike Gresens (msg-72) wrote :

Same problem since upgrade to Ubuntu 17.04

tags: added: bugpattern-needed
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
tags: added: artful
Daniel van Vugt (vanvugt) wrote :

Bumped importance. This bug is the #1 apport crash by an order of magnitude...

Changed in apport (Ubuntu):
importance: Medium → High
description: updated
summary: - apport-gtk crashed with SIGSEGV
+ apport-gtk crashed with SIGSEGV in
+ _gtk_style_provider_private_get_settings(provider=0x0)
summary: apport-gtk crashed with SIGSEGV in
+ [gtkstyleproviderprivate.c:123]
Changed in gtk+3.0 (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Changed in gtk:
importance: Unknown → High
status: Unknown → Confirmed
Changed in gtk+3.0 (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
status: Confirmed → In Progress
Changed in gtk+3.0 (Ubuntu):
assignee: Daniel van Vugt (vanvugt) → nobody
status: In Progress → Confirmed
tags: added: bionic
Changed in gtk:
status: Confirmed → Expired
tags: added: cosmic
Tom Reynolds (tomreyn) wrote :

I do not know how priorities in bug handling are set, but I do wonder what may be the reason to not handle this rather common (30 dupes) critical (crash) bug on a 'main' package for the past three years - could someone explain this to me? Thanks in advance.

Daniel van Vugt (vanvugt) wrote :

Now tracking in

I submitted a fix in 2017 but unfortunately it was not accepted.

Changed in gtk:
importance: High → Unknown
status: Expired → Unknown
Changed in gtk:
status: Unknown → New
To post a comment you must log in.