Bug 1028766

Summary: [abrt] xfwm4-4.10.1-1.fc19: strcmp: Process /usr/bin/xfwm4 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Cristian Ciupitu <cristian.ciupitu>
Component: xfwm4Assignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8872316d9faba2e7f0923fe6c7531c73c9f3ce2c
Whiteboard: abrt_hash:061f64e2cab888035a4642e7826cb9db36916458
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:10:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Cristian Ciupitu 2013-11-10 15:26:03 UTC
Version-Release number of selected component:
xfwm4-4.10.1-1.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        xfwm4 --display :0.0 --sm-client-id 21434d81f-b1b6-4884-9354-5dc8c765f699
crash_function: strcmp
executable:     /usr/bin/xfwm4
kernel:         3.11.7-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 strcmp at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:164
 #1 clientTerminate at client.c:2582
 #2 terminateProcessIO at terminate.c:82
 #7 gtk_main at gtkmain.c:1257

Potential duplicate: bug 803047

Comment 1 Cristian Ciupitu 2013-11-10 15:26:10 UTC
Created attachment 822091 [details]
File: backtrace

Comment 2 Cristian Ciupitu 2013-11-10 15:26:15 UTC
Created attachment 822092 [details]
File: cgroup

Comment 3 Cristian Ciupitu 2013-11-10 15:26:18 UTC
Created attachment 822093 [details]
File: core_backtrace

Comment 4 Cristian Ciupitu 2013-11-10 15:26:20 UTC
Created attachment 822094 [details]
File: dso_list

Comment 5 Cristian Ciupitu 2013-11-10 15:26:23 UTC
Created attachment 822095 [details]
File: environ

Comment 6 Cristian Ciupitu 2013-11-10 15:26:26 UTC
Created attachment 822096 [details]
File: exploitable

Comment 7 Cristian Ciupitu 2013-11-10 15:26:29 UTC
Created attachment 822097 [details]
File: limits

Comment 8 Cristian Ciupitu 2013-11-10 15:26:32 UTC
Created attachment 822098 [details]
File: maps

Comment 9 Cristian Ciupitu 2013-11-10 15:26:35 UTC
Created attachment 822099 [details]
File: open_fds

Comment 10 Cristian Ciupitu 2013-11-10 15:26:38 UTC
Created attachment 822100 [details]
File: proc_pid_status

Comment 11 Cristian Ciupitu 2013-11-10 15:26:40 UTC
Created attachment 822101 [details]
File: var_log_messages

Comment 12 Cristian Ciupitu 2013-11-10 15:32:14 UTC
It looks like ABRT wasn't smart enough that this is a duplicate of bug #949631
although on the other hand that one was reported for Fedora 18, not 19.

Comment 13 Cristian Ciupitu 2013-11-10 15:41:03 UTC
I've reported the bug upstream.

Comment 14 Fedora End Of Life 2015-01-09 20:33:00 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 15 Fedora End Of Life 2015-02-17 19:10:33 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.

Comment 16 Cristian Ciupitu 2015-02-17 19:52:11 UTC
For the record, this issue still exists in Fedora 20 as bug #949631.