Xwayland crashed with SIGABRT in __libc_start_call_main()

Bug #1952619 reported by Jonathan Kamens
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xwayland (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Probably relevant to bug 1952556.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: xwayland 2:21.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 29 08:58:02 2021
ExecutablePath: /usr/bin/Xwayland
InstallationDate: Installed on 2019-08-16 (835 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.KEYXD1 -listen 4 -listen 5 -displayfd 6 -initfd 7
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: xwayland
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_call_main (main=main@entry=0x561686440f50, argc=argc@entry=16, argv=argv@entry=0x7fff3a119e98) at ../sysdeps/nptl/libc_start_call_main.h:58
 __libc_start_main_impl (main=0x561686440f50, argc=16, argv=0x7fff3a119e98, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3a119e88) at ../csu/libc-start.c:409
Title: Xwayland crashed with SIGABRT in __libc_start_call_main()
UpgradeStatus: Upgraded to jammy on 2021-11-09 (20 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726
separator:

Revision history for this message
Jonathan Kamens (jik) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #1751508, 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
Jonathan Kamens (jik) wrote :

It's hard to see why the retracing service marked this as a duplicate of 1751508. I'm fairly certain it is not.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent Xwayland crashes on that page? If so then please send the links to us.

Changed in xwayland (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also ensure you have libmutter >= 40.5-1ubuntu3 for bug 1948894.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

See also bug 1952708 (currently private)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

After getting an identical Xwayland crash on my own machine today I can confirm it really is bug 1751508.

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.