Description of problem: Editing a new document in gedit. Version-Release number of selected component: gedit-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: gedit crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.12.9-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:545 #1 thread_memory_magazine1_alloc at gslice.c:848 #2 g_slice_alloc at gslice.c:1007 #3 gdk_threads_add_idle_full at gdk.c:888 #4 _gdk_synthesize_crossing_events_for_geometry_change at gdkwindow.c:8233 #5 gdk_window_show_internal at gdkwindow.c:4762 #6 update_grip_visibility at gtkwindow.c:7034 #7 _gtk_window_set_allocation at gtkwindow.c:6744 #8 gtk_window_size_allocate at gtkwindow.c:6766 #9 gtk_application_window_real_size_allocate at gtkapplicationwindow.c:734 Potential duplicate: bug 750087
Created attachment 860832 [details] File: backtrace
Created attachment 860833 [details] File: cgroup
Created attachment 860834 [details] File: core_backtrace
Created attachment 860835 [details] File: dso_list
Created attachment 860836 [details] File: environ
Created attachment 860837 [details] File: exploitable
Created attachment 860838 [details] File: limits
Created attachment 860839 [details] File: maps
Created attachment 860840 [details] File: open_fds
Created attachment 860841 [details] File: proc_pid_status
Created attachment 860842 [details] File: var_log_messages
Another user experienced a similar problem: Opening gedit from a shell logged with a different user is logged on gdm reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: gedit JobManager_trace.log crash_function: magazine_chain_pop_head executable: /usr/bin/gedit kernel: 3.13.3-201.fc20.x86_64 package: gedit-3.10.3-1.fc20 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1006
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.