Bug 1473894

Summary: [abrt] ibus-m17n: ibus_config_get_values(): ibus-engine-m17n killed by signal 6
Product: [Fedora] Fedora Reporter: Ildar Akhmetgaleev <akhilman>
Component: ibus-m17nAssignee: Parag Nemade <pnemade>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: akhilman, i18n-bugs, pnemade, shawn.p.huang
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b1da4670597f00dfab2c6542caa035058540cb25
Whiteboard: abrt_hash:d2f025994d83b982b87702335b3b9a744e411e5b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-04 07:39:58 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: cpuinfo
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

Description Ildar Akhmetgaleev 2017-07-22 06:40:31 UTC
Description of problem:
Fresh GNOME startup after full system freeze.
Catch this first time.

Version-Release number of selected component:
ibus-m17n-1.3.4-22.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/ibus-engine-m17n --ibus
crash_function: ibus_config_get_values
executable:     /usr/libexec/ibus-engine-m17n
journald_cursor: s=873f68b423cd490e8b16c77127889b8d;i=c64;b=3ac22d18f6a04a9c95712ed897a3a44f;m=12454652;t=554dfb2f42817;x=dfc2686ad512da51
kernel:         4.11.10-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 Ildar Akhmetgaleev 2017-07-22 06:40:37 UTC
Created attachment 1302645 [details]
File: backtrace

Comment 2 Ildar Akhmetgaleev 2017-07-22 06:40:39 UTC
Created attachment 1302646 [details]
File: cgroup

Comment 3 Ildar Akhmetgaleev 2017-07-22 06:40:41 UTC
Created attachment 1302647 [details]
File: core_backtrace

Comment 4 Ildar Akhmetgaleev 2017-07-22 06:40:42 UTC
Created attachment 1302648 [details]
File: cpuinfo

Comment 5 Ildar Akhmetgaleev 2017-07-22 06:40:44 UTC
Created attachment 1302649 [details]
File: dso_list

Comment 6 Ildar Akhmetgaleev 2017-07-22 06:40:46 UTC
Created attachment 1302650 [details]
File: environ

Comment 7 Ildar Akhmetgaleev 2017-07-22 06:40:47 UTC
Created attachment 1302651 [details]
File: limits

Comment 8 Ildar Akhmetgaleev 2017-07-22 06:40:49 UTC
Created attachment 1302652 [details]
File: maps

Comment 9 Ildar Akhmetgaleev 2017-07-22 06:40:51 UTC
Created attachment 1302653 [details]
File: open_fds

Comment 10 Ildar Akhmetgaleev 2017-07-22 06:40:52 UTC
Created attachment 1302654 [details]
File: proc_pid_status

Comment 11 Ildar Akhmetgaleev 2017-07-22 06:40:54 UTC
Created attachment 1302655 [details]
File: var_log_messages

Comment 12 Parag Nemade 2017-07-22 08:41:24 UTC
I request you to provide the input method file /usr/share/m17n/ru-kbd-plus.mim that created this crash.

Comment 13 Ildar Akhmetgaleev 2017-07-22 08:58:17 UTC
Yeah. This is my home made keyboard layout.
https://github.com/akhilman/dotfiles-desktop/blob/master/.m17n.d/ru-kbd-plus.mim

I have no problems with this layout in FC25 and Debian.

Comment 14 Parag Nemade 2018-01-03 11:23:30 UTC
revisiting this bug again.

May I know if this bug exists in Fedora 27 as well? I suspect this may be related to ibus but not to ibus-m17n as we have the same ibus-m17n package since Fedora 21/22.

Comment 15 Ildar Akhmetgaleev 2018-01-04 07:16:40 UTC
Unfortunately I have not fedora instances right now and can not test it.
But since this report I used my keyboard layout in fedora 26 for few months without any fault.

Comment 16 Parag Nemade 2018-01-04 07:39:58 UTC
Thank you for your prompt reply. I will close this now.