Bug 1085082

Summary: [abrt] xfwm4: strcmp(): xfwm4 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Fidel Leon <fidelleon>
Component: xfwm4Assignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: a.j.buxton, fidelleon, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/560a4bda790c0a8940f60a700eaae105e8903d37
Whiteboard: abrt_hash:061f64e2cab888035a4642e7826cb9db36916458
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:19:24 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 Fidel Leon 2014-04-07 18:55:36 UTC
Description of problem:
I tried to stop a hung application.

Version-Release number of selected component:
xfwm4-4.10.1-2.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        xfwm4 --display :0.0 --sm-client-id 291505996-4091-48cc-8826-bfdf591f2145
crash_function: strcmp
executable:     /usr/bin/xfwm4
kernel:         3.15.0-0.rc0.git5.2.fc21.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 strcmp at ../sysdeps/i386/i686/strcmp.S:33
 #1 clientTerminate at client.c:2582
 #2 terminateProcessIO at terminate.c:82
 #3 g_io_unix_dispatch at giounix.c:165
 #8 gtk_main at gtkmain.c:1257

Potential duplicate: bug 803047

Comment 1 Fidel Leon 2014-04-07 18:55:41 UTC
Created attachment 883726 [details]
File: backtrace

Comment 2 Fidel Leon 2014-04-07 18:55:43 UTC
Created attachment 883727 [details]
File: cgroup

Comment 3 Fidel Leon 2014-04-07 18:55:47 UTC
Created attachment 883728 [details]
File: core_backtrace

Comment 4 Fidel Leon 2014-04-07 18:55:50 UTC
Created attachment 883729 [details]
File: dso_list

Comment 5 Fidel Leon 2014-04-07 18:55:52 UTC
Created attachment 883730 [details]
File: environ

Comment 6 Fidel Leon 2014-04-07 18:55:54 UTC
Created attachment 883731 [details]
File: exploitable

Comment 7 Fidel Leon 2014-04-07 18:55:56 UTC
Created attachment 883732 [details]
File: limits

Comment 8 Fidel Leon 2014-04-07 18:55:59 UTC
Created attachment 883733 [details]
File: maps

Comment 9 Fidel Leon 2014-04-07 18:56:01 UTC
Created attachment 883734 [details]
File: open_fds

Comment 10 Fidel Leon 2014-04-07 18:56:04 UTC
Created attachment 883735 [details]
File: proc_pid_status

Comment 11 Fidel Leon 2014-04-07 18:56:06 UTC
Created attachment 883736 [details]
File: var_log_messages

Comment 12 Alistair Buxton 2014-11-05 20:06:43 UTC
Hi,

This bug happens because your hostname is 33 characters, and Xfwm has a silly hardcoded limit of 31 characters. I have submitted a patch upstream to fix this.

The bug you flagged as a potention duplicate is also the same issue.

Upstream bug report: https://bugzilla.xfce.org/show_bug.cgi?id=11282

Comment 13 Alistair Buxton 2014-11-06 12:01:17 UTC
Also, it would be helpful if you could verify the patch fixes the issue for you.

Comment 14 Alistair Buxton 2014-11-07 12:36:48 UTC
No need to verify now. The fix has been applied upstream.

http://git.xfce.org/xfce/xfwm4/commit/?id=19e9cc2db222fde7f138de86f3cedcda4a4d4295

Comment 15 Kevin Fenzi 2014-11-08 17:30:50 UTC
We might want to carry the patch until upstream does another point release... 

thanks a lot for tracking this down.

Comment 16 Alistair Buxton 2014-11-09 20:30:10 UTC
There is some discussion about the correctness of my first patch, see

https://bugzilla.xfce.org/show_bug.cgi?id=11289

which has an additional patch. Comments welcome.

Comment 17 Jaroslav Reznik 2015-03-03 17:00:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 18 Fedora End Of Life 2016-07-19 11:19:24 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.