gnome-control-center crashed with SIGSEGV

Bug #1725999 reported by jbchalier
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 17.10. On a new update from ubuntu 17.04.
version of the package is 1:3.26.1-0ubuntu4

Crashed after setting my google account. I clicked on the Facebook button to fill in the parameter and nothing...

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 14:29:43 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2015-10-25 (728 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x7f2828748b3b: mov 0x8(%rax),%rax
 PC (0x7f2828748b3b) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
Title: gnome-control-center crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
jbchalier (jbchalier) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1725972, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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