Date: Sat, 14 Nov 2020 15:09:23 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 251136] x11-wm/xfce4-wm: 4.14.6 fix crash on hang application kill via context menu Message-ID: <bug-251136-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251136 Bug ID: 251136 Summary: x11-wm/xfce4-wm: 4.14.6 fix crash on hang application kill via context menu Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: xfce@FreeBSD.org Reporter: rozhuk.im@gmail.com Flags: maintainer-feedback?(xfce@FreeBSD.org) Assignee: xfce@FreeBSD.org Created attachment 219680 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D219680&action= =3Dedit patch If I try to kill/end hanged app via context menu then after app die xfwm4 c= ore dumps: /usr/local/bin/xfwm4 --display unix:0.0 --sm-client-id 2d88326ee-d7fc-11e5-8d34-6cf0497538e3 --replace Waiting for current window manager (Xfwm4) on screen unix:0.0 to exit: Done (xfwm4:9573): Gdk-ERROR **: 17:39:45.446: The program 'xfwm4' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 78074 error_code 2 request_code 113 (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.) Trace/BPT trap (core dumped) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251136-7788>