Xwayland crashed with SIGABRT in __libc_start_call_main() when lock screen or screen blank

Bug #2035057 reported by Martin Randau
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xwayland (Ubuntu)
New
Undecided
Unassigned

Bug Description

When blank/lock screen in wayland. Crashes consistently each time, sessions ends and user it returned to gdm. Does not happen in xorg, OR when an external monitor is connected in wayland.

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: xwayland 2:23.2.0-1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Sep 11 08:19:38 2023
ExecutablePath: /usr/bin/Xwayland
InstallationDate: Installed on 2023-09-07 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907)
ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/124/.mutter-Xwaylandauth.OVN0A2 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients
Signal: 6
SourcePackage: xwayland
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_call_main (main=main@entry=0x55cc526fb030, argc=argc@entry=17, argv=argv@entry=0x7ffc9b2936f8) at ../sysdeps/nptl/libc_start_call_main.h:58
 __libc_start_main_impl (main=0x55cc526fb030, argc=17, argv=0x7ffc9b2936f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc9b2936e8) at ../csu/libc-start.c:360
Title: Xwayland crashed with SIGABRT in __libc_start_call_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

Revision history for this message
Martin Randau (cmmrandau) 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
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.