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

Bug #1933811 reported by Douglas Busch
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ayatana-indicator-printers (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Got a bug report. I don't know what it is.

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: ayatana-indicator-printers 0.8.2-1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Jun 28 11:09:14 2021
ExecutablePath: /usr/libexec/ayatana-indicator-printers/ayatana-indicator-printers-service
InstallationDate: Installed on 2021-06-28 (0 days ago)
InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210628)
ProcCmdline: /usr/libexec/ayatana-indicator-printers/ayatana-indicator-printers-service
SegvAnalysis:
 Segfault happened at: 0x7fbe471843ac <__GI_____strtol_l_internal+60>: movsbq 0x0(%r13),%rax
 PC (0x7fbe471843ac) 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=0x7fbe4731f4c0 <_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
XsessionErrors:
 mate-session[1157]: WARNING: Unable to find provider '' of required component 'dock'
 (process:1604): ayatana-indicator-sound-WARNING **: 11:09:12.120: volume-control-pulse.vala:745: Unable to connect to dbus server at 'unix:path=/run/user/1000/pulse/dbus-socket': Could not connect: No such file or directory
 (caja:1489): Gtk-WARNING **: 11:09:12.130: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
separator:

Revision history for this message
Douglas Busch (douglasbusch-gmail) wrote :
tags: removed: need-amd64-retrace
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ayatana-indicator-printers (Ubuntu):
status: New → Confirmed
tags: added: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI_____strtol_l_internal (nptr=0x0, endptr=endptr@entry=0x0, base=base@entry=10, group=group@entry=0, loc=0x7fbe4731f4c0 <_nl_global_locale>) at ../stdlib/strtol_l.c:292
 __strtol (nptr=<optimized out>, endptr=endptr@entry=0x0, base=base@entry=10) at ../stdlib/strtol.c:106
 atoi (__nptr=<optimized out>) at /usr/include/stdlib.h:363
 update_all_printer_menuitems (self=0x55f21985c1e0) at indicator-printers-menu.c:218
 g_type_plugin_use () from /tmp/apport_sandbox_ges_rgy3/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6800.3

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!

Changed in ayatana-indicator-printers (Ubuntu):
status: Confirmed → Invalid
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.