Bug 1008034

Summary: [abrt] geany-1.23.1-1.fc18: __strcmp_sse42: Process /usr/bin/geany was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Frank Dittrich <frank_dittrich>
Component: geanyAssignee: Josef Bacik <josef>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dmaphy, fdc, jonathan.underwood, josef
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5efe88a751d0b727b3954f442a7e7580a0cd9522
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:23:27 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 Frank Dittrich 2013-09-13 21:04:35 UTC 
Description of problem:
$ /usr/bin/geany
Segmentation fault (core dumped)

see https://bugzilla.redhat.com/show_bug.cgi?id=1003300 for more details

Version-Release number of selected component:
geany-1.23.1-1.fc18

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        geany
crash_function: __strcmp_sse42
executable:     /usr/bin/geany
kernel:         3.10.10-100.fc18.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 __strcmp_sse42 at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:233
 #1 _gtk_icon_cache_has_icon at gtkiconcache.c:353
 #2 gtk_icon_theme_has_icon at gtkicontheme.c:1588
 #3 gtk_action_group_add_actions_full at gtkactiongroup.c:1048
 #4 gtk_action_group_add_actions at gtkactiongroup.c:965
 #5 toolbar_init at toolbar.c:351
 #6 main_init at main.c:269
Comment 1 Frank Dittrich 2013-09-13 21:04:40 UTC 
Created attachment 797529 [details]
File: backtrace
Comment 2 Frank Dittrich 2013-09-13 21:04:43 UTC 
Created attachment 797530 [details]
File: cgroup
Comment 3 Frank Dittrich 2013-09-13 21:04:47 UTC 
Created attachment 797531 [details]
File: core_backtrace
Comment 4 Frank Dittrich 2013-09-13 21:04:50 UTC 
Created attachment 797532 [details]
File: dso_list
Comment 5 Frank Dittrich 2013-09-13 21:04:53 UTC 
Created attachment 797533 [details]
File: environ
Comment 6 Frank Dittrich 2013-09-13 21:04:57 UTC 
Created attachment 797534 [details]
File: exploitable
Comment 7 Frank Dittrich 2013-09-13 21:05:00 UTC 
Created attachment 797535 [details]
File: limits
Comment 8 Frank Dittrich 2013-09-13 21:05:05 UTC 
Created attachment 797536 [details]
File: maps
Comment 9 Frank Dittrich 2013-09-13 21:05:09 UTC 
Created attachment 797537 [details]
File: open_fds
Comment 10 Frank Dittrich 2013-09-13 21:05:12 UTC 
Created attachment 797538 [details]
File: proc_pid_status
Comment 11 Frank Dittrich 2013-09-13 21:05:15 UTC 
Created attachment 797539 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2013-12-21 14:35:11 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 13 Fedora End Of Life 2014-02-05 22:23:27 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.