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

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

Bug Description

I clicked on "Printers" and it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: gnome-control-center 1:3.20.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
Uname: Linux 4.8.0-15-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 28 03:00:13 2016
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2016-04-07 (173 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3d4f3b1f06 <strlen+38>: movdqu (%rax),%xmm4
 PC (0x7f3d4f3b1f06) ok
 source "(%rax)" (0xffffffffa1274cbc) 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-23 (4 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jason Hunter (jhunterwu) 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.