Ubuntu
ayatana-indicator-printers package

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

Bug #1928667 reported by Leó Kolbeinsson on 2021-05-17

This bug report is a duplicate of: Bug #1916377: ayatana-indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal(). Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	ayatana-indicator-printers (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

After rebooting fresh install Ubuntu Mate Impish daily ISO 17-05-2021

I received the error :Sorry,Ubuntu has experienced an internal error - send report to developers etc "

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: ayatana-indicator-printers 0.8.2-1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu66
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon May 17 10:36:08 2021
ExecutablePath: /usr/libexec/ayatana-indicator-printers/ayatana-indicator-printers-service
InstallationDate: Installed on 2021-05-17 (0 days ago)
InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210517)
ProcCmdline: /usr/libexec/ayatana-indicator-printers/ayatana-indicator-printers-service
SegvAnalysis:
Segfault happened at: 0x7feceacc43ac <__GI_____strtol_l_internal+60>: movsbq 0x0(%r13),%rax
PC (0x7feceacc43ac) 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=0x7feceae5f4c0 <_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[1151]: WARNING: Unable to find provider '' of required component 'dock'
(process:1632): ayatana-indicator-sound-WARNING **: 10:36:07.522: 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:1539): Gtk-WARNING **: 10:36:07.859: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
separator:

Tags:

Revision history for this message

Leó Kolbeinsson (leok) wrote on 2021-05-17:

Dependencies.txt Edit (7.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.3 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (11.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (305 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (69.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (8.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2021-05-17

tags:

removed: need-amd64-retrace

Leó Kolbeinsson (leok) on 2021-08-29

information type:

Private → Public

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2021-08-29:

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/1928667

tags:

added: iso-testing

Revision history for this message

Apport retracing service (apport) wrote on 2021-09-21: 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:	New → Invalid

Revision history for this message

Brian Murray (brian-murray) wrote on 2021-09-21:

I saw this bug was added to the iso tracker today, unfortunately this crash report is quite old and did not retrace successfully. Could you please open a new crash report from a fresh install? Thanks in advance!

Revision history for this message

Leó Kolbeinsson (leok) wrote on 2021-09-22:

I filed a new bug report #1944517
as requested but it was marked as a duplicate of bug #1916377.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1916377 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuayatana-indicator-printers package

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

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
ayatana-indicator-printers package

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