Xwayland crashed with SIGABRT in __libc_start_call_main()

Bug #1952708 reported by Daniel van Vugt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xwayland (Ubuntu)
New
Undecided
Unassigned

Bug Description

Probably a duplicate but we need to log this to get some retracing.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: xwayland 2:21.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 30 14:06:00 2021
ExecutablePath: /usr/bin/Xwayland
InstallationDate: Installed on 2021-11-05 (24 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.8LTQD1 -listen 4 -listen 5 -displayfd 6 -initfd 7
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: xwayland
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_call_main (main=main@entry=0x55f575b61f50, argc=argc@entry=16, argv=argv@entry=0x7ffe55669888) at ../sysdeps/nptl/libc_start_call_main.h:58
 __libc_start_main_impl (main=0x55f575b61f50, argc=16, argv=0x7ffe55669888, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7ffe55669878) at ../csu/libc-start.c:409
Title: Xwayland crashed with SIGABRT in __libc_start_call_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Daniel van Vugt (vanvugt) 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
Daniel van Vugt (vanvugt) wrote :

See also bug 1952619

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.