Bug 1368592

Summary: [abrt] ibus: panel_switch_engine(): ibus-ui-gtk3 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: laolux
Component: ibusAssignee: fujiwara <tfujiwar>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: i18n-bugs, laolux, oviswana, shawn.p.huang, smaitra, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5ae17c38689a32f5948e9d9a447bd2ce17aa6031
Whiteboard: abrt_hash:c610af2d18b3ac622330c8bb625f62c9f1afb80c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 16:38:00 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description laolux 2016-08-19 21:13:00 UTC
Version-Release number of selected component:
ibus-1.5.13-3.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        /usr/libexec/ibus-ui-gtk3
crash_function: panel_switch_engine
executable:     /usr/libexec/ibus-ui-gtk3
global_pid:     3966
kernel:         4.6.6-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 panel_switch_engine at panel.c:2989
 #1 keybinding_manager_event_handler at keybindingmanager.c:659
 #2 _keybinding_manager_event_handler_gdk_event_func at keybindingmanager.c:156
 #3 _gdk_event_emit at gdkevents.c:73
 #9 gtk_main at gtkmain.c:1269
 #10 application_run at application.c:199
 #11 application_main at application.c:269

Comment 1 laolux 2016-08-19 21:13:06 UTC
Created attachment 1192301 [details]
File: backtrace

Comment 2 laolux 2016-08-19 21:13:07 UTC
Created attachment 1192302 [details]
File: cgroup

Comment 3 laolux 2016-08-19 21:13:08 UTC
Created attachment 1192303 [details]
File: core_backtrace

Comment 4 laolux 2016-08-19 21:13:10 UTC
Created attachment 1192304 [details]
File: dso_list

Comment 5 laolux 2016-08-19 21:13:11 UTC
Created attachment 1192305 [details]
File: environ

Comment 6 laolux 2016-08-19 21:13:12 UTC
Created attachment 1192306 [details]
File: exploitable

Comment 7 laolux 2016-08-19 21:13:14 UTC
Created attachment 1192307 [details]
File: limits

Comment 8 laolux 2016-08-19 21:13:15 UTC
Created attachment 1192308 [details]
File: maps

Comment 9 laolux 2016-08-19 21:13:17 UTC
Created attachment 1192309 [details]
File: mountinfo

Comment 10 laolux 2016-08-19 21:13:18 UTC
Created attachment 1192310 [details]
File: namespaces

Comment 11 laolux 2016-08-19 21:13:19 UTC
Created attachment 1192311 [details]
File: open_fds

Comment 12 laolux 2016-08-19 21:13:21 UTC
Created attachment 1192312 [details]
File: proc_pid_status

Comment 13 laolux 2016-08-19 21:13:22 UTC
Created attachment 1192313 [details]
File: var_log_messages

Comment 14 fujiwara 2016-08-23 05:39:35 UTC
I cannot reproduce your backtrace.
Are still able to reproduce your backtrace?

(In reply to laolux from comment #1)
> Created attachment 1192301 [details]
> File: backtrace


#0  0x00005598d06d25ba in panel_switch_engine (self=0x5598d28d8300, i=<optimized out>, force=0) at panel.c:2989
        force = 0
        i = 2
        self = 0x5598d28d8300
2989		_tmp9_ = _tmp7_[_tmp8_];
#1  0x00005598d06ceeb4 in keybinding_manager_event_handler (event=0x5598d2b2c430, self=<optimized out>) at keybindingmanager.c:659
#2  _keybinding_manager_event_handler_gdk_event_func (event=0x5598d2b2c430, self=<optimized out>) at keybindingmanager.c:156
No locals.
#3  0x00007f0b602c90c5 in _gdk_event_emit (event=event@entry=0x5598d2b2c430) at gdkevents.c:73
No locals.
#4  0x00007f0b602f60b2 in gdk_event_source_dispatch (source=source@entry=0x5598d28dbc60, callback=<optimized out>, user_data=<optimized out>) at gdkeventsource.c:367
#5  0x00007f0b5e26e703 in g_main_dispatch (context=0x5598d28e95e0) at gmain.c:3154
#6  g_main_context_dispatch (context=context@entry=0x5598d28e95e0) at gmain.c:3769

Comment 15 laolux 2016-09-06 22:16:44 UTC
I am sorry, I can not get it to crash again.
It has happened to me a couple of times (3 at least before I report), but seemingly arbitrary, so I have no clue what caused it and can not reproduce it.

Comment 16 Fedora End Of Life 2017-07-25 22:31:34 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 2017-08-08 16:38:00 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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 18 ompragash 2017-08-24 10:06:10 UTC
Cannot reproduce. Feel free to reopen if anyone can reproduce this issue with "How to reproduce steps".