Bug 2290322 - [abrt] ibus-m17n: pop_im(): ibus-engine-m17n killed by SIGSEGV
Summary: [abrt] ibus-m17n: pop_im(): ibus-engine-m17n killed by SIGSEGV
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-m17n
Version: 40
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mike FABIAN
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:2deacdc1a5691e3d276b97fbd7b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-04 04:34 UTC by Nirmal Pathak
Modified: 2024-07-13 11:42 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-13 11:42:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: os_info (734 bytes, text/plain)
2024-06-04 04:34 UTC, Nirmal Pathak 		no flags Details
File: exploitable (81 bytes, text/plain)
2024-06-04 04:34 UTC, Nirmal Pathak 		no flags Details
File: environ (1.43 KB, text/plain)
2024-06-04 04:34 UTC, Nirmal Pathak 		no flags Details
File: cpuinfo (3.13 KB, text/plain)
2024-06-04 04:34 UTC, Nirmal Pathak 		no flags Details
File: dso_list (661 bytes, text/plain)
2024-06-04 04:35 UTC, Nirmal Pathak 		no flags Details
File: limits (1.29 KB, text/plain)
2024-06-04 04:35 UTC, Nirmal Pathak 		no flags Details
File: open_fds (1.09 KB, text/plain)
2024-06-04 04:35 UTC, Nirmal Pathak 		no flags Details
File: maps (3.98 KB, text/plain)
2024-06-04 04:35 UTC, Nirmal Pathak 		no flags Details
File: proc_pid_status (1.48 KB, text/plain)
2024-06-04 04:35 UTC, Nirmal Pathak 		no flags Details
File: mountinfo (2.96 KB, text/plain)
2024-06-04 04:35 UTC, Nirmal Pathak 		no flags Details
File: backtrace (39.36 KB, text/plain)
2024-06-04 04:35 UTC, Nirmal Pathak 		no flags Details
File: core_backtrace (15.59 KB, text/plain)
2024-06-04 04:35 UTC, Nirmal Pathak 		no flags Details
View All

Description Nirmal Pathak 2024-06-04 04:34:47 UTC 
Version-Release number of selected component:
ibus-m17n-1.4.29-1.fc40

Additional info:
reporter:       libreport-2.17.15
executable:     /usr/libexec/ibus-engine-m17n
cmdline:        /usr/libexec/ibus-engine-m17n --ibus
journald_cursor: s=675abb625b83480b8e6127c8b7cd20fa;i=2164db8;b=4267c74b66fd4dc3969efc28e47e0e69;m=670e1c704;t=619fbbe622828;x=2a3443f6d7f8831a
rootdir:        /
reason:         ibus-engine-m17n killed by SIGSEGV
type:           CCpp
package:        ibus-m17n-1.4.29-1.fc40
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.freedesktop.IBus.session.GNOME.service
runlevel:       N 5
kernel:         6.8.11-300.fc40.x86_64
uid:            1000
crash_function: pop_im

Truncated backtrace:
Thread no. 1 (17 frames)
 #0 pop_im at /usr/src/debug/m17n-lib-1.8.4-3.fc40.x86_64/src/input.c:3764
 #1 fini_ic_info at /usr/src/debug/m17n-lib-1.8.4-3.fc40.x86_64/src/input.c:3920
 #2 destroy_ic at /usr/src/debug/m17n-lib-1.8.4-3.fc40.x86_64/src/input.c:4073
 #3 minput_destroy_ic at /usr/src/debug/m17n-lib-1.8.4-3.fc40.x86_64/src/input.c:4923
 #4 fini_ic_info at /usr/src/debug/m17n-lib-1.8.4-3.fc40.x86_64/src/input.c:3930
 #5 re_init_ic at /usr/src/debug/m17n-lib-1.8.4-3.fc40.x86_64/src/input.c:4005
 #6 minput_callback at /usr/src/debug/m17n-lib-1.8.4-3.fc40.x86_64/src/input.c:6949
 #7 ibus_m17n_engine_focus_out at /usr/src/debug/ibus-m17n-1.4.29-1.fc40.x86_64/src/engine.c:905
 #8 ibus_m17n_engine_disable at /usr/src/debug/ibus-m17n-1.4.29-1.fc40.x86_64/src/engine.c:933
 #10 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3928
 #11 signal_emit_valist_unlocked at ../gobject/gsignal.c:3520
 #14 ibus_engine_service_method_call at /usr/src/debug/ibus-1.5.30-1.fc40.x86_64/src/ibusengine.c:1357
 #15 call_in_idle_cb at ../gio/gdbusconnection.c:5454
 #18 g_main_context_dispatch_unlocked at ../glib/gmain.c:4152
 #19 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4217
 #21 ibus_main at /usr/src/debug/ibus-1.5.30-1.fc40.x86_64/src/ibusshare.c:330
 #22 start_component at /usr/src/debug/ibus-m17n-1.4.29-1.fc40.x86_64/src/main.c:80


Potential duplicate: bug 2219580
Comment 1 Nirmal Pathak 2024-06-04 04:34:52 UTC 
Created attachment 2036213 [details]
File: os_info
Comment 2 Nirmal Pathak 2024-06-04 04:34:54 UTC 
Created attachment 2036214 [details]
File: exploitable
Comment 3 Nirmal Pathak 2024-06-04 04:34:56 UTC 
Created attachment 2036215 [details]
File: environ
Comment 4 Nirmal Pathak 2024-06-04 04:34:58 UTC 
Created attachment 2036216 [details]
File: cpuinfo
Comment 5 Nirmal Pathak 2024-06-04 04:35:01 UTC 
Created attachment 2036217 [details]
File: dso_list
Comment 6 Nirmal Pathak 2024-06-04 04:35:03 UTC 
Created attachment 2036218 [details]
File: limits
Comment 7 Nirmal Pathak 2024-06-04 04:35:05 UTC 
Created attachment 2036219 [details]
File: open_fds
Comment 8 Nirmal Pathak 2024-06-04 04:35:07 UTC 
Created attachment 2036220 [details]
File: maps
Comment 9 Nirmal Pathak 2024-06-04 04:35:09 UTC 
Created attachment 2036221 [details]
File: proc_pid_status
Comment 10 Nirmal Pathak 2024-06-04 04:35:11 UTC 
Created attachment 2036222 [details]
File: mountinfo
Comment 11 Nirmal Pathak 2024-06-04 04:35:13 UTC 
Created attachment 2036223 [details]
File: backtrace
Comment 12 Nirmal Pathak 2024-06-04 04:35:16 UTC 
Created attachment 2036224 [details]
File: core_backtrace
Comment 13 Parag Nemade 2024-07-08 04:28:27 UTC 
How to reproduce this reported issue?
Any steps you can provide us?
Comment 14 Nirmal Pathak 2024-07-10 13:31:54 UTC 
(In reply to Parag Nemade from comment #13)
> How to reproduce this reported issue?
> Any steps you can provide us?

Sorry, I do not know how to reproduce this. If I remember correctly, this happened only once.
Comment 15 Parag Nemade 2024-07-13 11:42:42 UTC 
Thank you for your reply. 
In case any crash happens again, do report new bug with the steps to reproduce it.
Note You need to log in before you can comment on or make changes to this bug.