Ubuntu
gnome-control-center package

gnome-control-center crashed with SIGSEGV

Bug #1724011 reported by John Ashley
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

added google account, then switched to new tab in settings.

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: Mon Oct 16 19:35:17 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-10-16 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x7f087bd3fb3b: mov 0x8(%rax),%rax
 PC (0x7f087bd3fb3b) 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/r600_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
Title: gnome-control-center crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
John Ashley (johnashleyftw) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 update_buffers (dri2_surf=dri2_surf@entry=0x561fd48b9d00) at ../../../src/egl/drivers/dri2/platform_wayland.c:541
 image_get_buffers (driDrawable=<optimized out>, format=<optimized out>, stamp=<optimized out>, loaderPrivate=0x561fd48b9d00, buffer_mask=<optimized out>, buffers=0x7fff6332ae60) at ../../../src/egl/drivers/dri2/platform_wayland.c:669
 dri_image_drawable_get_buffers (statts_count=<optimized out>, statts=<optimized out>, images=<optimized out>, drawable=<optimized out>) at ../../../../../src/gallium/state_trackers/dri/dri2.c:454
 dri2_allocate_textures (ctx=0x561fd43d5bd0, drawable=0x561fd4929ab0, statts=0x561fd492a120, statts_count=1) at ../../../../../src/gallium/state_trackers/dri/dri2.c:578
 dri_st_framebuffer_validate (stctx=<optimized out>, stfbi=<optimized out>, statts=0x561fd492a120, count=1, out=0x7fff6332b010) at ../../../../../src/gallium/state_trackers/dri/dri_drawable.c:85

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
Jean-Baptiste Lallement (jibel)
information type: Private → Public
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
Revision history for this message
Andrea Azzarone (azzar1) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1720400, so it 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. Feel free to continue to report any other bugs you may find.

Revision history for this message
Alan Munro (alanhmunro) wrote :

playing solitaire at the time. All appears normal.

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

Just added Google account in Online Accounts in Control Center, and Control Center crashed. Despite the crash, the Google account was added successfully and seems to be working.

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

Other bug subscribers

Remote bug watches

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