Marco crashed after closing MATE Tweak panel

Bug #1872538 reported by Aaron Pickett
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
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_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd93aebe655 <meta_frame_get_frame_bounds+21>: mov 0x8(%r8),%r8
 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_get_frame_bounds () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 meta_window_get_frame_bounds () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
Title: marco crashed with SIGSEGV in meta_frame_get_frame_bounds()
UpgradeStatus: Upgraded to focal on 2020-04-13 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Aaron Pickett (aaron-d-pickett) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

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.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 meta_frame_get_frame_bounds (frame=0x558750196640) at core/frame.c:410
 meta_window_get_frame_bounds (window=0x5587500fca00) at core/window.c:8917
 border_size (cw=0x558750496940) at compositor/compositor-xrender.c:1154
 paint_windows (region=10495493, root_pixmap=<optimized out>, root_buffer=<optimized out>, windows=<optimized out>, screen=0x55875018bd00) at compositor/compositor-xrender.c:1424
 paint_all (screen=screen@entry=0x55875018bd00, region=region@entry=10495493, b=<optimized out>) at compositor/compositor-xrender.c:1597

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in marco (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

I can't reproduce this issue in Ubuntu MATE 22.04

information type: Private → Public
Changed in marco (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for marco (Ubuntu) because there has been no activity for 60 days.]

Changed in marco (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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