Description of problem: 1. I use gedit to edit a existing file ( I am upload it later) 2. I selected one of Chinese characters 3. I pressed Super + Space to switch to ibus-chewing input engine which I set with GNOME Settings. 4. I pressed "j" key with ibus-chewing 5. gedit crashed Version-Release number of selected component: gedit-3.8.1-1.fc19 Additional info: backtrace_rating: 4 cmdline: gedit /home/zerng07/Translations/anjuta.gnome-3-8.zh_TW.po crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.9.0-0.rc8.git0.2.fc19.x86_64 runlevel: N 5 uid: 1000 ureports_counter: 1 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:532 #1 thread_memory_magazine1_alloc at gslice.c:835 #2 g_slice_alloc at gslice.c:994 #3 pango_attr_list_new at pango-attributes.c:1113 #4 pango_attr_list_filter at pango-attributes.c:1992 #5 filter_no_shape_attributes at pango-layout.c:3812 #6 pango_layout_check_lines at pango-layout.c:3872 #7 pango_layout_get_extents_internal at pango-layout.c:2534 #8 pango_layout_get_extents at pango-layout.c:2729 #9 gtk_text_layout_get_line_display at gtktextlayout.c:2438 Potential duplicate: bug 750087
Created attachment 741062 [details] File: backtrace
Created attachment 741063 [details] File: cgroup
Created attachment 741064 [details] File: core_backtrace
Created attachment 741065 [details] File: dso_list
Created attachment 741066 [details] File: environ
Created attachment 741068 [details] File: limits
Created attachment 741069 [details] File: maps
Created attachment 741070 [details] File: open_fds
Created attachment 741071 [details] File: proc_pid_status
Created attachment 741072 [details] File: var_log_messages
Created attachment 741083 [details] The file which I edited from.
Steps to reproduce ================== 1. Launch gedit 2. Open a file in any format whose syntax gedit can recognize to highlight the text 3. Move the cursor to any position where strings highlighted 4. Input Japanese characters through ibus and try to convert them with the space key there, and gedit cranshes reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gedit crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.9.8-300.fc19.x86_64 package: gedit-3.8.3-1.fc19 reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
100% reproducible, with the following * Install some tex related packages, ibus, ibus-kkc * $ gedit tmp.txt * On the window - type $$ - go to head - type ctrl-space, entering ibus-kkc mode - type "ima" - enter space to convert "Ima" to kanji - then crash reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gedit crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.10.3-300.fc19.i686 package: gedit-3.8.3-1.fc19 reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV) runlevel: 3 5 uid: 500
CC-ing to i18n, because it seems this issue is affecting several people using ibus on CJK locale.
Created attachment 781795 [details] screenshot just before gedit crashes (In reply to Jiro Matsuzawa from comment #12) > Steps to reproduce > ================== > 2. Open a file in any format whose syntax gedit can recognize to highlight > the text With my steps, when typing "ima" before $$, "ima" is highlightened (see screenshot)
Created attachment 781796 [details] correct screenshot The above screenshot was wrong, sorry
This issue has been fixed on the upstream. [1][2] [1] https://bugzilla.gnome.org/show_bug.cgi?id=703533 [2] https://git.gnome.org/browse/gtk+/commit/?id=837a0d3e4002e640be2aea2a67802c474997e354
(In reply to Jiro Matsuzawa from comment #17) > This issue has been fixed on the upstream. [1][2] > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=703533 > [2] > https://git.gnome.org/browse/gtk+/commit/ > ?id=837a0d3e4002e640be2aea2a67802c474997e354 Confirmed that applying this patch to gtk3-3.8.2-2.fc19.src resolves this issue.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.