Ubuntu
gnome-control-center package

gnome-control-center crashed with SIGSEGV in gtk_label_set_markup() from check_wpad_warning() from g_cclosure_marshal_VOID__STRINGv()

Bug #1873165 reported by rustam on 2020-04-16

28

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-control-center (Ubuntu)	Confirmed	Low	Unassigned

Bug Description

https://errors.ubuntu.com/problem/3fa64649544784debafc88b54f81b5d6ffa6fdad

---

AMD Ryzen 5 2500U with vega 8 gpx

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 8 18:10:46 2020
ExecutablePath: /usr/bin/gnome-control-center
ExecutableTimestamp: 1586127615
InstallationDate: Installed on 2020-04-08 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcCmdline: gnome-control-center
ProcCwd: /home/rustam
SegvAnalysis:
Segfault happened at: 0x7fcb540c777b <gtk_label_set_markup+43>: cmp %rsi,(%rax)
PC (0x7fcb540c777b) ok
source "%rsi" ok
destination "(%rax)" (0x800000004) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
gtk_label_set_markup () from /lib/x86_64-linux-gnu/libgtk-3.so.0
?? ()
g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_label_set_markup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

See original description

Tags:

Revision history for this message

rustam (afaritovich) wrote on 2020-04-16:

#1

Dependencies.txt Edit (20.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (129.4 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (290 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (215.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (7.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (54.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2020-04-16:

#2

StacktraceTop:
gtk_label_set_markup (label=0x556369a413f0, str=0x55636924b020 "") at ../../../../gtk/gtklabel.c:2803
check_wpad_warning (self=0x5563695b8870) at ../panels/network/net-proxy.c:124
g_cclosure_marshal_VOID__STRINGv () from /tmp/apport_sandbox_3kzykwsq/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6400.1
_g_closure_invoke_va () from /tmp/apport_sandbox_3kzykwsq/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6400.1
g_signal_emit_valist () from /tmp/apport_sandbox_3kzykwsq/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6400.1

Revision history for this message

Apport retracing service (apport) wrote on 2020-04-16: Stacktrace.txt

#3

Stacktrace.txt Edit (18.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2020-04-16: StacktraceSource.txt

#4

StacktraceSource.txt Edit (13.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2020-04-16: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (67.6 KiB, text/plain)

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

Revision history for this message

Sebastien Bacher (seb128) wrote on 2020-04-16: Re: gnome-control-center crashed with SIGSEGV in gtk_label_set_markup()

#6

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

information type:	Private → Public
Changed in gnome-control-center (Ubuntu):
importance:	Medium → Low
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2020-06-16:

#7

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-control-center (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-06-16:

#8

Tracking in:

https://errors.ubuntu.com/problem/3fa64649544784debafc88b54f81b5d6ffa6fdad

summary:	- gnome-control-center crashed with SIGSEGV in gtk_label_set_markup() + gnome-control-center crashed with SIGSEGV in gtk_label_set_markup() from + check_wpad_warning() from g_cclosure_marshal_VOID__STRINGv()
Changed in gnome-control-center (Ubuntu):
status:	Expired → Confirmed
description:	updated

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #1883648

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.