Bug 1389940

Summary: [abrt] xfwm4: clientCycleEventFilter(): xfwm4 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Benjamin Ariel Nava Martinez <arielnmz>
Component: xfwm4Assignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: kevin, lslebodn, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fa777b992257f16c9d6c084c043c3446d6c047b5
Whiteboard: abrt_hash:2a907cc0a493764a1e26831b600c358fc6a7be0f;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:03:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Benjamin Ariel Nava Martinez 2016-10-29 18:05:15 UTC 
Version-Release number of selected component:
xfwm4-4.12.3-3.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        xfwm4 --display :0.0 --sm-client-id 2c775083a-3ba7-477c-a6a5-cb2bb6f8a631
crash_function: clientCycleEventFilter
executable:     /usr/bin/xfwm4
global_pid:     1333
kernel:         4.7.9-200.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 clientCycleEventFilter at cycle.c:264
 #1 eventXfwmFilter at event_filter.c:158
 #2 gdk_event_apply_filters at gdkevents-x11.c:371
 #3 gdk_event_translate at gdkevents-x11.c:969
 #4 _gdk_events_queue at gdkevents-x11.c:2358
 #10 gtk_main at gtkmain.c:1268
 #11 clientCycle at cycle.c:509
 #12 handleKeyPress at events.c:329
 #13 handleEvent at events.c:2196
 #14 xfwm4_event_filter at events.c:2297

Potential duplicate: bug 1336228
Comment 1 Benjamin Ariel Nava Martinez 2016-10-29 18:05:21 UTC 
Created attachment 1215387 [details]
File: backtrace
Comment 2 Benjamin Ariel Nava Martinez 2016-10-29 18:05:22 UTC 
Created attachment 1215388 [details]
File: cgroup
Comment 3 Benjamin Ariel Nava Martinez 2016-10-29 18:05:24 UTC 
Created attachment 1215389 [details]
File: core_backtrace
Comment 4 Benjamin Ariel Nava Martinez 2016-10-29 18:05:25 UTC 
Created attachment 1215390 [details]
File: dso_list
Comment 5 Benjamin Ariel Nava Martinez 2016-10-29 18:05:26 UTC 
Created attachment 1215391 [details]
File: environ
Comment 6 Benjamin Ariel Nava Martinez 2016-10-29 18:05:27 UTC 
Created attachment 1215392 [details]
File: exploitable
Comment 7 Benjamin Ariel Nava Martinez 2016-10-29 18:05:28 UTC 
Created attachment 1215393 [details]
File: limits
Comment 8 Benjamin Ariel Nava Martinez 2016-10-29 18:05:30 UTC 
Created attachment 1215394 [details]
File: maps
Comment 9 Benjamin Ariel Nava Martinez 2016-10-29 18:05:31 UTC 
Created attachment 1215395 [details]
File: mountinfo
Comment 10 Benjamin Ariel Nava Martinez 2016-10-29 18:05:32 UTC 
Created attachment 1215396 [details]
File: namespaces
Comment 11 Benjamin Ariel Nava Martinez 2016-10-29 18:05:33 UTC 
Created attachment 1215397 [details]
File: open_fds
Comment 12 Benjamin Ariel Nava Martinez 2016-10-29 18:05:34 UTC 
Created attachment 1215398 [details]
File: proc_pid_status
Comment 13 Benjamin Ariel Nava Martinez 2016-10-29 18:05:35 UTC 
Created attachment 1215399 [details]
File: var_log_messages
Comment 14 Kevin Fenzi 2016-10-31 02:12:06 UTC 
What were you doing when this happened?

Can you duplicate the crash?
Comment 15 Lukas Slebodnik 2017-05-21 10:21:58 UTC 
It crashed for me as well xfwm4-4.12.4-1.fc26
and it crashed after firefox crashed.
Comment 16 Fedora End Of Life 2017-07-25 23:40:10 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 17 Fedora End Of Life 2017-08-08 19:03:12 UTC 
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.