gnome-control-center crashed with SIGSEGV in strlen() when printing in Ubuntu GNOME 16.10 Yakkety
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.fedoraproje
Sep 26 21:42:52 ubuntu-gnome org.fedoraproje
Sep 26 21:42:52 ubuntu-gnome org.fedoraproje
Sep 26 21:42:52 ubuntu-gnome org.fedoraproje
So I installed system-
Selecting the printer icon again in settings now produces this crash
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: gnome-control-
ProcVersionSign
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/
LiveMediaBuild: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
ProcCmdline: gnome-control-
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f8f0b455f06 <strlen+38>: movdqu (%rax),%xmm4
PC (0x7f8f0b455f06) ok
source "(%rax)" (0xffffffffa60f
destination "%xmm4" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
strlen () at ../sysdeps/
g_strdup () from /lib/x86_
?? ()
?? () from /usr/lib/
g_signal_
Title: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.