Ubuntu
ayatana-indicator-messages package

ayatana-indicator-messages package

Bug #2013051 reported by Gene Soo on 2023-03-28

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ayatana-indicator-messages (Ubuntu)	New	Undecided	Unassigned

Bug Description

Unknown error with no description.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: ayatana-indicator-messages 22.9.0-1
Uname: Linux 6.2.0-18-generic x86_64
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Mar 28 05:15:39 2023
ExecutablePath: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service
ExecutableTimestamp: 1664708325
ProcCmdline: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service
ProcCwd: /home/gene
ProcEnviron:
LANG=en_US.UTF-8
LANGUAGE=en_US
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
Signal: 11
SourcePackage: ayatana-indicator-messages
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

Tags:

Revision history for this message

Gene Soo (genesoo77072) wrote on 2023-03-28:

Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Gene Soo (genesoo77072) wrote on 2023-03-28:

Error occurred on first boot of Ubuntu MATE 2304 Daily Build after installation.

Revision history for this message

Apport retracing service (apport) wrote on 2023-03-28: This bug is a duplicate

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 #2003251, 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.

information type:	Private → Public
tags:	removed: need-amd64-retrace

Revision history for this message

Gene Soo (genesoo77072) wrote on 2023-03-28:

I accidentally removed the duplicate link to 2003251. This incident # was indicated as Private and I was not able to drill into it to review the comments. I am unable to link this back to that incident. If someone else who has higher authority and can re-establish that linkage, I would appreciate it. I hope I would get some notification on the resolution.