I've got a 100% reproducible crash[1] with Firefox on Wayland, but
I've run into a brick wall getting it properly reported.
Neither coredumpctl nor abrt even report a crash, so no coredump file
exists. I was advised in my bug report that abrt doesn't provide
useful information anyway [1], so I should collect it directly with
gdb.
The problem I then encountered: the laptop becomes a hair dryer and
unresponsive for at least 60 minutes with zero crash information
written out, so I gave up. I've processed coredumps from other
applications before with gdb, it usually takes less than a minute.
Anyway, it seems like a problem if possibly the most popular
application on Fedora is this difficult to debug.
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1678897
[2]
https://bugzilla.redhat.com/show_bug.cgi?id=1676331#c2
--
Chris Murphy