indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()

[Hugo de Almeida Cocharro]

NOT SURE, just after upgrade this problem occured, without event trying to print

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 17:20:58 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
InstallationDate: Installed on 2016-12-10 (314 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
SegvAnalysis:
 Segfault happened at: 0x7ff89cfc8be5 <__GI_____strtol_l_internal+53>: movsbq (%r14),%rax
 PC (0x7ff89cfc8be5) ok
 source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-printers
StacktraceTop:
 __GI_____strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=<optimized out>, loc=0x7ff89d366520 <_nl_global_locale>) at ../stdlib/strtol_l.c:292
 ()
 g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev pico plugdev sambashare scanner sudo tape video

[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 #1703046, 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.