Is the crash mentioned in syslogs? If yes, can you find a reason stated there? I have seen coredumps not stored for several reasons such as coredump being larger than specified limits, or problems with limits (nproc / number of pipes).
Interestingly, for me, the post renders correctly, not as horrible as in @barryascott’s post.
@barryascott, apologies. It does for me, too, in retrospect.
I authored this with VS Code, and was confident enough of my CommonMark skills that I didn’t confirm that it looked correct after posting it. Additionally, when I posted it at GitHub, it sanitised it, as most places appear to:
I’ve since encapsulated it within a pre > code, which appears to remediate this!
0138:err:seh:call_seh_handlers invalid frame 00000001000FA620 (0000000000122000-0000000000320000)
0138:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.
013c:fixme:winediag:loader_init wine-staging 11.0 is a testing version containing experimental patches.
013c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.
…with pwsh, all that journalctl -f reports is a coredump, for powershell:
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY kwin_wayland[2052]: QProcess: Destroyed while process ("/usr/libexec/kwin_killer_helper") is still running.
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY powershell[28655]: (7.5.4-0-g7c8d9e7e0ed2fc1f2caf50746fe9fef720ca2a0a:1:80) [Perftrack_ConsoleStartupStart:PowershellConsoleStartup.WinStart.Informational] PowerShell console is starting up
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit[28655]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=28655 comm="pwsh" exe="/usr/lib64/powershell/pwsh" sig=6 res=1
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd-coredump[28672]: Process 28655 (pwsh) of user 1000 terminated abnormally with signal 6/ABRT, processing...
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=305 op=LOAD
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=306 op=LOAD
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=307 op=LOAD
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd[1]: Started systemd-coredump@33-45062-28672_28673-0.service - Process Core Dump (PID 28672/UID 0).
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@33-45062-28672_28673-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=308 op=LOAD
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=309 op=LOAD
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=310 op=LOAD
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd[1]: Started drkonqi-coredump-processor@33-45062-28672_28673-0.service - Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
May 07 14:49:30 Beedell.RokeJulianLockhart.desktop.SSV2AY audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=drkonqi-coredump-processor@33-45062-28672_28673-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd-coredump[28673]: Removed old coredump core.pwsh.1000.3d0db8fa19f8483d8262762f73da107a.1041064.1778106292000000.zst.
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY abrt-dump-journal-core[1460]: Failed to obtain all required information from journald
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY abrt-dump-journal-core[1460]: Failed to obtain all required information from journald
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd-coredump[28673]: [🡕] Process 28655 (pwsh) of user 1000 dumped core.
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd[1]: systemd-coredump@33-45062-28672_28673-0.service: Deactivated successfully.
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@33-45062-28672_28673-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd[1]: systemd-coredump@33-45062-28672_28673-0.service: Consumed 528ms CPU time over 548ms wall clock time, 167.9M memory peak.
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=307 op=UNLOAD
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=306 op=UNLOAD
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=305 op=UNLOAD
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd[1779]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=drkonqi-coredump-processor@33-45062-28672_28673-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY drkonqi-coredump-processor[28674]: socket state unexpectedly QLocalSocket::UnconnectedState aborting crash processing
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd[1]: drkonqi-coredump-processor@33-45062-28672_28673-0.service: Deactivated successfully.
May 07 14:49:31 Beedell.RokeJulianLockhart.desktop.SSV2AY systemd[1]: drkonqi-coredump-processor@33-45062-28672_28673-0.service: Consumed 82ms CPU time over 986ms wall clock time, 106.4M memory peak.
May 07 14:49:32 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=310 op=UNLOAD
May 07 14:49:32 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=309 op=UNLOAD
May 07 14:49:32 Beedell.RokeJulianLockhart.desktop.SSV2AY audit: BPF prog-id=308 op=UNLOAD
May 07 14:49:32 Beedell.RokeJulianLockhart.desktop.SSV2AY abrt-server[28685]: Deleting problem directory ccpp-2026-05-07-14:49:31.983060-28655 (dup of ccpp-2026-05-06-21:12:11.702637-659129)
May 07 14:49:33 Beedell.RokeJulianLockhart.desktop.SSV2AY abrt-applet[2850]: g_app_info_should_show: assertion 'G_IS_APP_INFO (appinfo)' failed
May 07 14:49:33 Beedell.RokeJulianLockhart.desktop.SSV2AY abrt-server[28685]: Can't generate stacktrace description (no crash thread?)
May 07 14:49:33 Beedell.RokeJulianLockhart.desktop.SSV2AY abrt-notification[28731]: [🡕] Process 659129 (pwsh) crashed in PROCAbort()
…which merely appears to be an example of:
Consequently, I’ve tried it in bash, too. With that, all that I observe is:
May 07 14:57:51 Beedell.RokeJulianLockhart.desktop.SSV2AYkwin_wayland[2052]: QProcess: Destroyed while process (“/usr/libexec/kwin_killer_helper”) is still running.
I don’t really see why that’s related. If it didn’t consistently appear immediately after the DE sending wine a SIGABRT upon ANR, I wouldn’t have mentioned it.
Now, this is more Wine-focussed, and whether it’s useful is not something that I am able to determine, but the potentially relevant excerpt of time strace -Ttr -- wine notepad’s output is:
This line indicates that the pwsh process is core dumping, and that this crash should be in coredumpctl’s list.
For whatever reason (maybe quota, i.e., maybe the coredumps take too much disk space? see man coredump.conf) the old coredump of pwsh has been deleted.
Anyways, it seems like at the end of your strace, the notepad process regularly exits. It seems like something decides that this is not a crash, but a termination – which wouldn’t show up in coredumpctl, because there was no coredump created. (I have seen this issue before with some wayland related bug: Firefox gave invalid data to Wayland, and wayland immediately terminated the application, i.e., it did not crash nor raise an exception or the like)
If you are interested, you could start notepad in gdb and set a breakpoint in exit_group, or maybe also in these if that is possible:
@christiansam, not categorising what is (presumably) a SigAbrt, from the DE, to be a crash, might be reasonable, considering that it’s merely an ANR, because until we solve the halting problem, expecting that it may resume is reasonable.
What’s strange, though, is that any other application (non-Wine, at least) would be caught by CoreDumpD, when it is killed via that signal.
I frequently see it with, specifically, Firefox, too. I’ll see it crash, see nothing in coredumpctl list -r or abrt list, then check firefox-nightly about:crashes, and see a few entries. Sometimes, these are even segmentation violations: [1]
I wonder what’s special about these two.
Yeah; it is. It’s probably a separate problem, considering that it appears to list a crash in some subsystem from even the slightest touch (even though it doesn’t visibly affect the shell). DotNet’s fragile.
Probably because I’ve so many, per the aforementioned. Though, it would also do that if Wine were creating a core dump, so that shouldn’t matter.
I don’t see notepad killed by a signal, only raising an Exception. Again, if it would be killed e.g. by SIGILL, it should be listed by coredumpctl, but – from the kernel’s perspective – the application just regularly exited as it should. In other words, notepad didn’t crash, it merely terminated itself in an unfavorable way.
@genodeftest, would you consider what the undermentioned depicts to be so?
Even qdbus-qt6 org.kde.Shutdown /Shutdown org.kde.Shutdown.logout whilst it’s in that state doesn’t make any difference. Perhaps, it just ignores the DE, and it happens to die approximately when the DE creates that ANR modal?