Bug 454072

Summary:	"Xwayland has crashed" when trying to start Discord
Product:	[Plasma] kwin	Reporter:	Lucia Mrenica <lucia.mrenica>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	crash	CC:	kde, lucia.mrenica
Priority:	NOR
Version First Reported In:	5.24.90
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Lucia Mrenica 2022-05-20 06:12:41 UTC

SUMMARY
This is possibly a Discord issue or Xwayland issue, but this issue doesn't exist on Gnome Wayland.
Trying to start Discord either native or Flatpak results in Discord not starting and above message appearing.

Comment 1 Lucia Mrenica 2022-05-20 06:13:21 UTC

This might be similar to 452243.

Comment 2 David Edmundson 2022-05-20 07:15:49 UTC

If Xwayland crashes it's an xwayland bug. Even if we're sending it wrong information it shouldn't crash.
Can you try and get a backtrace (coredumpctl?) and report there.

Comment 3 Lucia Mrenica 2022-05-20 07:25:19 UTC

(In reply to David Edmundson from comment #2)
> If Xwayland crashes it's an xwayland bug. Even if we're sending it wrong
> information it shouldn't crash.
> Can you try and get a backtrace (coredumpctl?) and report there.

Normally I would be able to do so, but even with debuginfod there is almost nothing in the backtraces.

Comment 4 Lucia Mrenica 2022-05-21 14:23:21 UTC

Just had the same issue with vlc, so this is not a discord issue. To clarify, vlc does start and can play an audio file, only the main window doesn't appear. Backtrace looks like this:

#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x00007f34e5a603d3 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#2  0x00007f34e5a10838 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3  0x00007f34e59fa535 in __GI_abort () at abort.c:79
#4  0x00005594e8e37981 in ?? ()
#5  0x00005594e8e4156d in ?? ()
#6  0x00005594e8e359d6 in ?? ()
#7  <signal handler called>
#8  0x00005594e8d060c9 in ?? ()
#9  0x00007f34e58da536 in ffi_call_unix64 () at ../src/x86/unix64.S:105
#10 0x00007f34e58d7037 in ffi_call_int (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>) at ../src/x86/ffi64.c:672
#11 0x00007f34e5f375e2 in wl_closure_invoke (closure=closure@entry=0x5594eaff9500, target=<optimized out>, target@entry=0x5594eb0ae790, opcode=opcode@entry=3, data=<optimized out>, 
    flags=<optimized out>) at ../wayland-1.20.0/src/connection.c:1025
#12 0x00007f34e5f37d73 in dispatch_event (display=display@entry=0x5594ea4b3b20, queue=<optimized out>, queue=<optimized out>) at ../wayland-1.20.0/src/wayland-client.c:1583
#13 0x00007f34e5f37f8c in dispatch_queue (queue=0x5594ea4b3bf0, display=0x5594ea4b3b20) at ../wayland-1.20.0/src/wayland-client.c:1729
#14 wl_display_dispatch_queue_pending (display=0x5594ea4b3b20, queue=0x5594ea4b3bf0) at ../wayland-1.20.0/src/wayland-client.c:1971
#15 0x00005594e8d0b3ed in ?? ()
#16 0x00005594e8e36e31 in ?? ()
#17 0x00005594e8d73ef0 in ?? ()
#18 0x00005594e8d018e0 in ?? ()
#19 0x00007f34e59fb290 in __libc_start_call_main (main=main@entry=0x5594e8d00080, argc=argc@entry=13, argv=argv@entry=0x7fffc0b15768) at ../sysdeps/nptl/libc_start_call_main.h:58
#20 0x00007f34e59fb34a in __libc_start_main_impl (main=0x5594e8d00080, argc=13, argv=0x7fffc0b15768, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, 
    stack_end=0x7fffc0b15758) at ../csu/libc-start.c:392
#21 0x00005594e8d03135 in ?? ()

Too many missing steps, right? Anyway is this the right site? https://bugs.freedesktop.org/describecomponents.cgi?product=Wayland Says zero bugs found.