[printers]: hostname-control-center crashed with SIGSEGV in g_slist_find()

[Thomas Hotz]

I wanted to install my new printer in Ubuntu GNOME 13.10 and then it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu39
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Mon Sep 30 18:59:48 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-30 (0 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Beta amd64 (20130929)
MarkForUpload: True
ProcCmdline: hostname-control-center --overview
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1e788f5b60 <g_slist_find+16>: cmp %rsi,(%rax)
 PC (0x7f1e788f5b60) ok
 source "%rsi" ok
 destination "(%rax)" (0x6e617078652d6261) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_slist_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_container_child_notify () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: [printers]: hostname-control-center crashed with SIGSEGV in g_slist_find()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

[Apport retracing service (apport)]

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 #1162804, 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.