Marco crashed after closing MATE Tweak panel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
marco (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
After rebooting following 20.04 beta install, I opened the MATE Tweak panel to see what compositor I was using (Marco adaptive. I closed this panel, and did nothing else. Shortly thereafter, marco crashed.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: marco 1.24.0-1ubuntu1
ProcVersionSign
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: MATE
Date: Mon Apr 13 13:14:49 2020
ExecutablePath: /usr/bin/marco
InstallationDate: Installed on 2019-12-08 (127 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcCmdline: marco
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fd93aebe655 <meta_frame_
PC (0x7fd93aebe655) ok
source "0x8(%r8)" (0x0000c83d) not located in a known VMA region (needed readable region)!
destination "%r8" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: marco
StacktraceTop:
meta_frame_
meta_window_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: marco crashed with SIGSEGV in meta_frame_
UpgradeStatus: Upgraded to focal on 2020-04-13 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
This crash has the same stack trace characteristics as bug #1863431. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.