gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

Bug #1717277 reported by Cristian Aravena Romero
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-control-center
Confirmed
Medium
gnome-online-accounts (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Hello,

I'm working with GNOME settings

Regards,
--
Cristian

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.25.92.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Sep 14 11:49:22 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-07-05 (70 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x7f3817fd1e32 <g_type_check_instance_cast+34>: mov (%rdi),%rbp
 PC (0x7f3817fd1e32) ok
 source "(%rdi)" (0x100000000) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 goa_object_peek_account () from /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=type_instance@entry=0x555ef9cedaf0, iface_type=93866403363680) at ../../../../gobject/gtype.c:4057
 goa_object_peek_account (object=0x555ef9cedaf0) at goa-generated.c:24246
 on_notification_closed (button=button@entry=0x0, self=0x555ef91887a0, self@entry=<error reading variable: value has been optimized out>) at cc-online-accounts-panel.c:911
 on_remove_account_timeout (user_data=<error reading variable: value has been optimized out>) at cc-online-accounts-panel.c:937
 g_timeout_dispatch (source=source@entry=0x555ef9b67000, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4633

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Changed in gnome-control-center:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Changed in gnome-control-center (Ubuntu):
status: Confirmed → Triaged
affects: gnome-control-center (Ubuntu) → gnome-online-accounts (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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