Red Hat Bugzilla – Bug 1278489
[abrt] xfwm4: XUnmapWindow(): xfwm4 killed by SIGSEGV
Last modified: 2015-12-02 13:21:26 EST
Description of problem:
1) It usually happens when opening a new tab in the google chrome version google-chrome-stable-46.0.2490.80-1.x86_64
2) the computer is stuck and needs to be powered off and on again
Version-Release number of selected component:
cmdline: xfwm4 --display :0.0 --sm-client-id 28429cd22-ab24-4770-8a8e-ccb03e3aad97
Thread no. 1 (10 frames)
#0 XUnmapWindow at UnmapWin.c:39
#1 wireframeUpdate at wireframe.c:56
#2 clientCycleEventFilter at cycle.c:337
#3 eventXfwmFilter at event_filter.c:158
#4 gdk_event_apply_filters at gdkevents-x11.c:371
#5 gdk_event_translate at gdkevents-x11.c:969
#6 _gdk_events_queue at gdkevents-x11.c:2358
#12 gtk_main at gtkmain.c:1268
#13 clientCycle at cycle.c:455
#14 xfwm4_event_filter at events.c:331
Potential duplicate: bug 971935
Created attachment 1090170 [details]
Created attachment 1090171 [details]
Created attachment 1090172 [details]
Created attachment 1090173 [details]
Created attachment 1090174 [details]
Created attachment 1090175 [details]
Created attachment 1090176 [details]
Created attachment 1090177 [details]
Created attachment 1090178 [details]
Created attachment 1090179 [details]
The crash happened in xlib. Reassigning.
(In reply to Raphael Groner from comment #11)
> The crash happened in xlib. Reassigning.
Just because the backtrace ends in XUnmapWindow does not mean that there is a bug there, likely there is some memory corruption hapening elsewhere, or a bad window handle is being passed in.
So changing back to xfwm4 again for now.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.