gnome-control-center crashed with SIGSEGV in strlen() when printing in Ubuntu GNOME 16.10 Yakkety

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

Bug Description

I'm trying to print in 16.10 Ubuntu GNOME - to print to a HP printer.

From the liveCD the message "failed to add new printer" is observed when selecting the settings-printer icon.

looking at journalctl -ae --full there is a message saying that:

Sep 26 21:42:52 ubuntu-gnome org.fedoraproject.Config.Printing[3725]: /usr/share/system-config-printer/scp-dbus-service.py:26: PyGIW
Sep 26 21:42:52 ubuntu-gnome org.fedoraproject.Config.Printing[3725]: from gi.repository import Gdk
Sep 26 21:42:52 ubuntu-gnome org.fedoraproject.Config.Printing[3725]: /usr/share/system-config-printer/scp-dbus-service.py:27: PyGIW
Sep 26 21:42:52 ubuntu-gnome org.fedoraproject.Config.Printing[3725]: from gi.repository import Gtk

So I installed system-control-printer-gnome

Selecting the printer icon again in settings now produces this crash

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: gnome-control-center 1:3.20.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
Uname: Linux 4.8.0-11-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CasperVersion: 1.378
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Sep 26 21:47:52 2016
ExecutablePath: /usr/bin/gnome-control-center
LiveMediaBuild: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8f0b455f06 <strlen+38>: movdqu (%rax),%xmm4
 PC (0x7f8f0b455f06) ok
 source "(%rax)" (0xffffffffa60f3bcc) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
fossfreedom (fossfreedom) wrote :
summary: - gnome-control-center crashed with SIGSEGV in strlen() when printing
+ gnome-control-center crashed with SIGSEGV in strlen() when printing in
+ Ubuntu GNOME 16.10 Yakkety
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
Revision history for this message
fossfreedom (fossfreedom) wrote :

Hi this is reported to be a duplicate - but there is no duplicate link. Please can this be updated with the link to the linked issue?

Revision history for this message
Jeremy Bícha (jbicha) wrote :

The problem is that crash bugs are private until a developer or bug triager with the rights access comes along and marks it as public. I've done that now for bug 1618290.

Revision history for this message
fossfreedom (fossfreedom) wrote :

Thanks Jeremy - happy to help to debug this for ubuntu gnome - we've seen this for budgie-remix users trying to print to HP printers as well.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thanks, David. Feel free to comment on bug 1618290 from now on.

I appreciate any help in figuring out what the problem is here.

I don't have a printer right now and the Printer Settings window doesn't crash for me when there's no printer configured.

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.