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

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

Bug Description

missed the printer-config function and reinstalled system-config-printer-gnome and common. system crashed while upgrading to 16.10. fonts were broken and needed to be reinstalled... i'll have to set up the system again.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: gnome-control-center 1:3.20.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Sep 5 20:10:28 2016
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2016-04-15 (143 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x7f9e6a309f06 <strlen+38>: movdqu (%rax),%xmm4
 PC (0x7f9e6a309f06) ok
 source "(%rax)" (0x0911fb2c) not located in a known VMA region (needed readable region)!
 destination "%xmm4" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in strlen()
UpgradeStatus: Upgraded to yakkety on 2016-09-03 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
starkus (starkus) 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 #1618290, 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.