Bug 1324864 - [abrt] ibus-gucharmap: character_to_iter(): ibus-engine-gucharmap killed by SIGSEGV
Summary: [abrt] ibus-gucharmap: character_to_iter(): ibus-engine-gucharmap killed by S...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-gucharmap
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daiki Ueno
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:1b62a9c37f0d3db0079fdbf4c4b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-07 13:14 UTC by perso
Modified: 2016-12-20 19:50 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-20 19:50:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (28.92 KB, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: cgroup (200 bytes, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: core_backtrace (7.99 KB, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: dso_list (7.81 KB, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: environ (1.67 KB, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: exploitable (82 bytes, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: limits (1.29 KB, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: maps (36.01 KB, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: mountinfo (3.15 KB, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: namespaces (85 bytes, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: open_fds (825 bytes, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: proc_pid_status (1.04 KB, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details
File: var_log_messages (28 bytes, text/plain)
2016-04-07 13:14 UTC, perso
no flags Details

Description perso 2016-04-07 13:14:00 UTC
Description of problem:
I just tried to use ibus-gucharmap and it didn't work.

Version-Release number of selected component:
ibus-gucharmap-1.4.0-12.fc23

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/libexec/ibus-engine-gucharmap --ibus
crash_function: character_to_iter
executable:     /usr/libexec/ibus-engine-gucharmap
global_pid:     2412
kernel:         4.4.6-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 character_to_iter at gucharmap-block-chapters-model.c:120
 #1 ibus_gucharmap_charmap_panel_real_activate_character at charmap-panel.c:468
 #2 g_cclosure_marshal_VOID__FLAGSv at gmarshal.c:1570
 #3 _g_closure_invoke_va at gclosure.c:864
 #5 g_signal_emit_by_name at gsignal.c:3479
 #6 ibus_gucharmap_charmap_panel_construct at charmap-panel.c:440
 #7 ibus_gucharmap_charmap_panel_new at charmap-panel.c:453
 #8 ibus_gucharmap_engine_constructor at engine.c:609
 #9 g_object_new_with_custom_constructor at gobject.c:1697
 #10 g_object_new_internal at gobject.c:1777

Comment 1 perso 2016-04-07 13:14:05 UTC
Created attachment 1144710 [details]
File: backtrace

Comment 2 perso 2016-04-07 13:14:06 UTC
Created attachment 1144711 [details]
File: cgroup

Comment 3 perso 2016-04-07 13:14:07 UTC
Created attachment 1144712 [details]
File: core_backtrace

Comment 4 perso 2016-04-07 13:14:09 UTC
Created attachment 1144713 [details]
File: dso_list

Comment 5 perso 2016-04-07 13:14:10 UTC
Created attachment 1144714 [details]
File: environ

Comment 6 perso 2016-04-07 13:14:12 UTC
Created attachment 1144715 [details]
File: exploitable

Comment 7 perso 2016-04-07 13:14:13 UTC
Created attachment 1144716 [details]
File: limits

Comment 8 perso 2016-04-07 13:14:15 UTC
Created attachment 1144717 [details]
File: maps

Comment 9 perso 2016-04-07 13:14:17 UTC
Created attachment 1144718 [details]
File: mountinfo

Comment 10 perso 2016-04-07 13:14:18 UTC
Created attachment 1144719 [details]
File: namespaces

Comment 11 perso 2016-04-07 13:14:19 UTC
Created attachment 1144720 [details]
File: open_fds

Comment 12 perso 2016-04-07 13:14:21 UTC
Created attachment 1144721 [details]
File: proc_pid_status

Comment 13 perso 2016-04-07 13:14:22 UTC
Created attachment 1144722 [details]
File: var_log_messages

Comment 14 Fedora End Of Life 2016-11-25 07:17:04 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 15 Fedora End Of Life 2016-12-20 19:50:57 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.


Note You need to log in before you can comment on or make changes to this bug.