mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mate-screensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
looks similar to bug 1943369, but that ticket is marked as fix released and I have the version with the fix installed
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: mate-screensaver 1.26.1-1
Uname: Linux 5.17.1-
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Apr 1 19:19:21 2022
ExecutablePath: /usr/bin/
ProcCmdline: /usr/bin/
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fe9e1661727 <matemenu_
PC (0x7fe9e1661727) ok
source "$0x1" ok
destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: mate-screensaver
StacktraceTop:
matemenu_
gs_theme_
()
()
g_closure_invoke () at /usr/lib/
Title: mate-screensaver crashed with SIGSEGV in matemenu_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom davfs2 dialout dip docker fax libvirt lpadmin microk8s plugdev sambashare src staff sudo
modified.
separator:
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 #1943369, 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.