Bug 1180802

Summary: [abrt] gcin: strcmp(): gcin killed by SIGSEGV
Product: [Fedora] Fedora Reporter: samuelleung123 <samuelleung123>
Component: gcinAssignee: Christopher Meng <i>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: i18n-bugs, i, psatpute, samuelleung123
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8bcfd59c537d50cb521e8010092e72b83bc86d0b
Whiteboard: abrt_hash:42b007e1484f38afa1ac3217d3b678865f10d625
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 07:10:26 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: exploitable none

Description samuelleung123 2015-01-10 11:45:40 UTC 
Description of problem:
I add an input method "帶調粵拼".It happened after I click "OK".

Version-Release number of selected component:
gcin-2.8.2-3.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        gcin
crash_function: strcmp
executable:     /usr/bin/gcin
kernel:         3.17.7-300.fc21.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 strcmp at ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S:240
 #1 set_wselkey_str at win1.cpp:467
 #2 set_wselkey at win1.cpp:502
 #3 gcin_FocusIn at eve.cpp:1578
 #4 process_client_req at im-dispatch.cpp:498
 #5 cb_read_gcin_client_data at im-srv.cpp:41
 #6 g_io_unix_dispatch at giounix.c:165
 #11 gtk_main at gtkmain.c:1257
Comment 1 samuelleung123 2015-01-10 11:45:44 UTC 
Created attachment 978502 [details]
File: backtrace
Comment 2 samuelleung123 2015-01-10 11:45:45 UTC 
Created attachment 978503 [details]
File: cgroup
Comment 3 samuelleung123 2015-01-10 11:45:46 UTC 
Created attachment 978504 [details]
File: core_backtrace
Comment 4 samuelleung123 2015-01-10 11:45:48 UTC 
Created attachment 978505 [details]
File: dso_list
Comment 5 samuelleung123 2015-01-10 11:45:49 UTC 
Created attachment 978506 [details]
File: environ
Comment 6 samuelleung123 2015-01-10 11:45:50 UTC 
Created attachment 978507 [details]
File: limits
Comment 7 samuelleung123 2015-01-10 11:45:52 UTC 
Created attachment 978508 [details]
File: maps
Comment 8 samuelleung123 2015-01-10 11:45:53 UTC 
Created attachment 978509 [details]
File: open_fds
Comment 9 samuelleung123 2015-01-10 11:45:54 UTC 
Created attachment 978510 [details]
File: proc_pid_status
Comment 10 samuelleung123 2015-01-10 11:45:56 UTC 
Created attachment 978511 [details]
File: var_log_messages
Comment 11 samuelleung123 2015-01-10 11:45:57 UTC 
Created attachment 978512 [details]
File: exploitable
Comment 12 Fedora End Of Life 2015-11-04 14:15:53 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 13 Pravin Satpute 2015-11-25 13:42:49 UTC 
Is this bug still exist in F23? Is not please close else move to F23. 
We don't want to loose any valuable bug :)

If this is non-reproducible please close it as worksforme.
Comment 14 Fedora End Of Life 2015-12-02 07:10:28 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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 15 Red Hat Bugzilla 2023-09-14 02:53:09 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days