Hide Forgot
Version-Release number of selected component: gedit-3.8.3-1.fc19 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: gedit '/home/deep/\xe6\xa1\x8c\xe9\x9d\xa2/\xe6\x96\xb0\xe6\x96\x87\xe4\xbb\xb6' crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.11.1-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 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_font_desc_new at pango-attributes.c:712 #4 add_text_attrs at gtktextlayout.c:1568 #5 gtk_text_layout_get_line_display at gtktextlayout.c:2282 #6 gtk_text_layout_get_iter_location at gtktextlayout.c:2898 #7 gtk_text_view_scroll_to_iter at gtktextview.c:2003 #8 gtk_text_view_flush_scroll at gtktextview.c:2232 #9 gtk_text_view_flush_first_validate at gtktextview.c:3903 Potential duplicate: bug 750087
Created attachment 802287 [details] File: backtrace
Created attachment 802288 [details] File: cgroup
Created attachment 802289 [details] File: core_backtrace
Created attachment 802290 [details] File: dso_list
Created attachment 802291 [details] File: environ
Created attachment 802292 [details] File: exploitable
Created attachment 802293 [details] File: limits
Created attachment 802294 [details] File: maps
Created attachment 802295 [details] File: open_fds
Created attachment 802296 [details] File: proc_pid_status
Created attachment 802297 [details] File: var_log_messages
this is Ibus(pinyin) problem which crashed very frequently... reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gedit EID.dat.r.sort crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.11.9-200.fc19.i686.PAE package: gedit-3.8.3-1.fc19 reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/JavaScriptContentOrder.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.19-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Excuting gedit. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/JavaScriptContentOrder.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.19-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: The gedit has closed when i was using the gedit. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/script_library/context.js /var/www/html/apmY/htdocs/script_library/test1.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.22-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I have met the problem changing english to hangul of keyboard in gedit. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/script_library/context.js /var/www/html/apmY/htdocs/script_library/test1.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.22-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: excuting gedit reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/script_library/context.js /var/www/html/apmY/htdocs/script_library/test1.html /var/www/html/apmY/htdocs/script_library/test2.html /var/www/html/apmY/htdocs/script_library/test3.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.22-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Using gedit reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/JavaScriptContentOrder.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.23-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Using gedit reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/script_library/context.js /var/www/html/apmY/htdocs/script_library/test1.html /var/www/html/apmY/htdocs/script_library/test2.html /var/www/html/apmY/htdocs/script_library/test3.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.23-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: typing in gedit reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/jQueryContent24.html /var/www/html/apmY/htdocs/jQueryContent24helper1.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.23-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: typeing in gedit reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/jQueryContentOrder.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.23-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: excuting gedit reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/jQueryContent27.html /var/www/html/apmY/htdocs/jQueryContent27helper12.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.23-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: changing english key to hangul key. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/jQueryContent28.html /var/www/html/apmY/htdocs/jQueryContent28helper1.html /var/www/html/apmY/htdocs/jQueryContent28helper2.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.23-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: using hangul keyboard mode reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/jQueryContent32.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.23-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.
Another user experienced a similar problem: inputting hangul reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/cgi-bin/trigger.php crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.27-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: inputting hangul in gedit reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gedit /var/www/html/apmY/htdocs/centertop.html crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.14.27-100.fc19.x86_64 package: gedit-3.8.3-2.fc19 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.