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

[Togo28]

Crash after start

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: ayatana-indicator-printers 0.8.2-1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: MATE
Date: Wed Sep 22 20:53:38 2021
ExecutablePath: /usr/libexec/ayatana-indicator-printers/ayatana-indicator-printers-service
InstallationDate: Installed on 2021-09-22 (0 days ago)
InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20210922)
ProcCmdline: /usr/libexec/ayatana-indicator-printers/ayatana-indicator-printers-service
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f71746e655c <__GI_____strtol_l_internal+60>: movsbq 0x0(%r13),%rax
 PC (0x7f71746e655c) ok
 source "0x0(%r13)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ayatana-indicator-printers
StacktraceTop:
 __GI_____strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=0, loc=0x7f71748b4560 <_nl_global_locale>) at ../stdlib/strtol_l.c:292
 ?? ()
 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: ayatana-indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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