marco crashed with signal 5 in _XReadEvents()

Bug #1943289 reported by navycat
92
This bug affects 14 people
Affects Status Importance Assigned to Milestone
marco (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Random crash of marco.

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: marco 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: MATE
Date: Sat Sep 11 01:39:03 2021
ExecutablePath: /usr/bin/marco
InstallationDate: Installed on 2021-05-28 (105 days ago)
InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210526)
ProcCmdline: marco
ProcEnviron:
 LANGUAGE=ru_RU
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: marco
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 _XReadEvents () from /lib/x86_64-linux-gnu/libX11.so.6
 XWindowEvent () from /lib/x86_64-linux-gnu/libX11.so.6
 meta_display_get_current_time_roundtrip () from /lib/x86_64-linux-gnu/libmarco-private.so.2
Title: marco crashed with signal 5 in _XReadEvents()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
navycat (navycatt) wrote :
Changed in marco (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 meta_display_get_current_time_roundtrip (display=display@entry=0x556eb9eb4910) at core/display.c:1237
 timestamp_too_old (display=display@entry=0x556eb9eb4910, window=window@entry=0x556eba114260, timestamp=timestamp@entry=0x7fff23fcf06c) at core/display.c:5413
 meta_display_set_input_focus_window (display=0x556eb9eb4910, window=0x556eba114260, focus_frame=0, timestamp=<optimized out>) at core/display.c:5454
 meta_window_focus (window=0x556eba114260, timestamp=0) at core/window.c:4449
 focus_ancestor_or_top_window (workspace=0x556eb9d64990, not_this_one=<optimized out>, timestamp=0) at core/workspace.c:1082

tags: removed: need-amd64-retrace
tags: added: jammy
information type: Private → Public
Revision history for this message
Ricardo Dias Marques (ricmarques) wrote :

So far, I also got this "marco crashed with signal 5 in _XReadEvents()" crash ("Sorry, Ubuntu 22.04 has experienced an internal error.") twice, in a laptop that I upgraded from Ubuntu 20.04.5 LTS ("Focal Fossa") to Ubuntu 22.04.1 LTS ("Jammy Jellyfish") about a week ago. In both times, the crash happened seconds after I logged in with my user in Ubuntu.

Here's some of the content in the associated "_usr_bin_marco.1000.crash" file in the "/var/crash" directory of the crash that happened to me today (1st September 2022):

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Thu Sep 1 01:20:52 2022
DistroRelease: Ubuntu 22.04
ExecutablePath: /usr/bin/marco
ExecutableTimestamp: 1649755698
ProcCmdline: marco
(...)
Package: marco 1.26.0-3ubuntu1
PackageArchitecture: amd64
(..)
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 _XReadEvents () from /lib/x86_64-linux-gnu/libX11.so.6
 XWindowEvent () from /lib/x86_64-linux-gnu/libX11.so.6
 meta_display_get_current_time_roundtrip () from /lib/x86_64-linux-gnu/libmarco-private.so.2
Tags: jammy
(...)
Title: marco crashed with signal 5 in _XReadEvents()
UpgradeStatus: Upgraded to jammy on 2022-08-27 (5 days ago)
(...)

Revision history for this message
André Letterer (andre-letterer) wrote :

Experienced here with most recent Jammy too.
The error only happens from time to time.

Attached Crash Dump

Revision history for this message
Felix Natter (fnatter) wrote :

Could we work around this by choosing another mate WM / marco variant
(Mate Tweak in preferences; i.e. one with compositing)?

Could someone please test whether that works / does not work?

Thanks and Best Regards,
Felix

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.