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

Bug #1916377 reported by Abram Daniel
120
This bug affects 17 people
Affects Status Importance Assigned to Milestone
ayatana-indicator-printers (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This report seams a little off, because printers drivers are fine?

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: ayatana-indicator-printers 0.8.2-1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Feb 21 02:29:19 2021
ExecutablePath: /usr/libexec/ayatana-indicator-printers/ayatana-indicator-printers-service
InstallationDate: Installed on 2020-12-04 (78 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha amd64 (20201112)
ProcCmdline: /usr/libexec/ayatana-indicator-printers/ayatana-indicator-printers-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1f8fb5c3bc <__GI_____strtol_l_internal+60>: movsbq 0x0(%r13),%rax
 PC (0x7f1f8fb5c3bc) 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=0x7f1f8fcf74c0 <_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 lxd plugdev sudo
separator:

Revision history for this message
Abram Daniel (adani802) wrote :
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=0x7f1f8fcf74c0 <_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=0x55d022a487a0) at indicator-printers-menu.c:218
 g_type_create_instance (type=<optimized out>) at ../../../gobject/gtype.c:1867

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ayatana-indicator-printers (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: impish
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
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1916377

tags: added: iso-testing
information type: Private → Public
Changed in ubuntu-mate:
status: New → Confirmed
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

This is still an issue on Ubuntu MATE 22.04 daily build, tested today.
I also marked other 5 instances of the same issue as duplicates of this one.

Revision history for this message
Leó Kolbeinsson (leok) wrote :

Testing Ubuntu Mate 22.04 Jammy build 16-12-2021 on Dell Optiplex 7040

This issue again present see test results : http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/241303/testcases/1300/results/

Revision history for this message
Leó Kolbeinsson (leok) wrote (last edit ):

Further to my last comment - screenshot of the error -

I did the updates - rebooted and again same error.

tags: added: jammy
Revision history for this message
Leó Kolbeinsson (leok) wrote :

This is still an issue on Ubuntu MATE Jammy daily build 2022-02-07 - tested today.

no longer affects: ubuntu-mate
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.