Version-Release number of selected component: gedit-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gedit /home/zerwan/Apks/freecyngn-flashable.zip crash_function: insert_run executable: /usr/bin/gedit kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 insert_run at pango-layout.c:3341 #7 process_item at pango-layout.c:3446 #8 process_line at pango-layout.c:3704 #9 pango_layout_check_lines at pango-layout.c:4027 #10 pango_layout_get_extents_internal at pango-layout.c:2587 #11 pango_layout_get_extents at pango-layout.c:2782 #12 gtk_text_layout_get_line_display at gtktextlayout.c:2446 #13 gtk_text_layout_real_wrap at gtktextlayout.c:1163 #14 gtk_text_btree_node_validate at gtktextbtree.c:5103 #19 _gtk_text_btree_validate at gtktextbtree.c:5255 Potential duplicate: bug 967405
Created attachment 842697 [details] File: backtrace
Created attachment 842698 [details] File: cgroup
Created attachment 842699 [details] File: core_backtrace
Created attachment 842700 [details] File: dso_list
Created attachment 842701 [details] File: environ
Created attachment 842702 [details] File: limits
Created attachment 842703 [details] File: maps
Created attachment 842704 [details] File: open_fds
Created attachment 842705 [details] File: proc_pid_status
Created attachment 842706 [details] File: var_log_messages
Another user experienced a similar problem: I dont' remember, it's something happened some days ago. I'm sorry! reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gedit /usr/share/desktop-directories/Settings-More.directory crash_function: insert_run executable: /usr/bin/gedit kernel: 3.12.6-300.fc20.x86_64 package: gedit-3.10.3-1.fc20 reason: gedit killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Tried to open an pdf document generated with texstudio-2.8.6/texlive-2013 with gedit-3.10.4. Tried multiple times, crashed every time. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gedit /home/holzstock/University/Repository/LaTeX/SCS/Lab2/lab2.pdf crash_function: insert_run executable: /usr/bin/gedit kernel: 3.16.6-203.fc20.i686+PAE package: gedit-3.10.4-1.fc20 reason: gedit killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: 140kB png image opened in gedit by wrong firefox mimetype association. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gedit crash_function: insert_run executable: /usr/bin/gedit kernel: 3.17.7-200.fc20.x86_64 package: gedit-3.10.4-1.fc20 reason: gedit killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.