Bug 949631

Summary: [abrt] xfwm4-4.10.0-5.fc18: 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: 20CC: admiller, fidelleon, kevin, vpodzime
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:061f64e2cab888035a4642e7826cb9db36916458
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:38:02 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
Application that goes ballistic once you push the "Hello" button none

Description Cristian Ciupitu 2013-04-08 16:34:50 UTC
Version-Release number of selected component:
xfwm4-4.10.0-5.fc18

Additional info:
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.8.5-201.fc18.x86_64
uid:            1000
ureports_counter: 1
xsession_errors: 

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 strcmp at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:162
 #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-04-08 16:34:53 UTC
Created attachment 732743 [details]
File: backtrace

Comment 2 Cristian Ciupitu 2013-04-08 16:34:56 UTC
Created attachment 732744 [details]
File: cgroup

Comment 3 Cristian Ciupitu 2013-04-08 16:34:59 UTC
Created attachment 732745 [details]
File: core_backtrace

Comment 4 Kevin Fenzi 2013-04-08 19:30:27 UTC
I guess this happened on logout? 

Does it happen on every logout? 

Can you duplicate it?

Comment 5 Cristian Ciupitu 2013-04-08 20:33:43 UTC
I haven't logged out for the last couple of days, so no.

It happened to me only once. I have no idea how can I reproduce it.

Comment 6 Cristian Ciupitu 2013-10-26 16:48:43 UTC
Created attachment 816406 [details]
Application that goes ballistic once you push the "Hello" button

Run the attached application, press the "Hello" button then try to close
it by pressing the x button from the title bar.  xfwm4 will crash.

Comment 7 Kevin Fenzi 2013-10-28 18:38:21 UTC
Neat. ;) 

Would you be willing to file this upstream? Or would you like me to do so...

Comment 8 Cristian Ciupitu 2013-11-01 17:40:27 UTC
Isn't this bug similar to https://bugzilla.xfce.org/show_bug.cgi?id=10365 ?

Comment 9 Kevin Fenzi 2013-11-01 19:13:39 UTC
It could be yeah... not sure.

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

Comment 11 Fedora End Of Life 2013-12-21 15:28:08 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 12 Kevin Fenzi 2013-12-22 15:52:57 UTC
*** Bug 1045771 has been marked as a duplicate of this bug. ***

Comment 13 Fidel Leon 2014-02-24 02:05:58 UTC
Another user experienced a similar problem:

Killed a non-working yumex window

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        xfwm4 --display :0.0 --sm-client-id 2092959fe-95c9-453d-9643-1436e2117095
crash_function: strcmp
executable:     /usr/bin/xfwm4
kernel:         3.13.3-201.fc20.x86_64
package:        xfwm4-4.10.1-2.fc20
reason:         xfwm4 killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Cristian Ciupitu 2014-03-02 20:22:34 UTC
It just happened to me again (according to ABRT).

Comment 15 Vratislav Podzimek 2014-03-24 19:59:41 UTC
Another user experienced a similar problem:

Tried to terminate an unresponsive application.

reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        xfwm4
crash_function: strcmp
executable:     /usr/bin/xfwm4
kernel:         3.13.4-200.fc20.i686
package:        xfwm4-4.10.1-2.fc20
reason:         xfwm4 killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Fedora End Of Life 2015-05-29 08:58:46 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2015-06-30 00:38:02 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.