Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#69095 - [xfwm4] xfwm4 crashes often when using ghidra

Attached to Project: Arch Linux
Opened by Iru Dog (mytbk) - Friday, 25 December 2020, 05:29 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 30 December 2020, 07:40 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


xfwm4 often crashes when using ghidra. dmesg says:

traps: xfwm4[2155] trap int3 ip:7faa07544294 sp:7ffef1298890 error:0 in[7faa07504000+8c000]

When running xfwm4 from terminal, I can get:

xfwm4-Message: 13:21:02.630: Prefer XPresent with Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2)

(xfwm4:2354): Gdk-ERROR **: 13:22:21.604: The program 'xfwm4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 108348 error_code 3 request_code 20 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

Additional info:
* package versions: xfwm4 4.16.0-1, glib2 2.66.4-1, ghidra 9.2-1

Steps to reproduce:
I don't know how to reproduce this exactly, but xfwm4 often crashes when opening a new window or closing a window in ghidra.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 30 December 2020, 07:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  xfwm4 4.16.0-2
Comment by Iru Dog (mytbk) - Friday, 25 December 2020, 05:30 GMT
A coredump here.
Comment by Iru Dog (mytbk) - Friday, 25 December 2020, 05:58 GMT
I've checked some upstream issues like It seems not related to this, which didn't happen before upgrading to xfwm 4.16.0.
Comment by Evangelos Foutras (foutrelis) - Friday, 25 December 2020, 07:24 GMT Comment by Evangelos Foutras (foutrelis) - Saturday, 26 December 2020, 07:33 GMT
This should be fixed in xfwm4 4.16.0-2.