indicator-messages-service crashed with SIGSEGV

[Thomas Boerner]

This happens after upgrade from 22.10 to 23.04. No idea what and why, sorry, it just appears

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: X-Cinnamon
Date: Tue Mar 28 20:21:02 2023
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
InstallationDate: Installed on 2022-06-12 (289 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
 Segfault happened at: 0x7fc5944c6419: cmp (%rax),%rsi
 PC (0x7fc5944c6419) ok
 source "(%rax)" (0x561c04bf02a4) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-messages
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: indicator-messages-service crashed with SIGSEGV
UpgradeStatus: Upgraded to lunar on 2023-03-27 (1 days ago)
UserGroups: vboxsf vboxusers
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 #2012879, 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.