Version-Release number of selected component: gedit-3.16.3-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gedit --gapplication-service crash_function: gca_scrollbar_marker_update_spacing executable: /usr/bin/gedit global_pid: 28872 kernel: 4.1.3-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gca_scrollbar_marker_update_spacing at src/gca-scrollbar-marker.c:237 #5 _g_closure_invoke_va at gclosure.c:831 #8 gtk_style_context_do_invalidate at gtkstylecontext.c:2868 #9 _gtk_style_context_validate at gtkstylecontext.c:3080 #23 gtk_container_idle_sizer at gtkcontainer.c:1856 #24 _g_closure_invoke_va at gclosure.c:831 #26 g_signal_emit_by_name at gsignal.c:3401 #27 gdk_frame_clock_paint_idle at gdkframeclockidle.c:408 #33 g_main_context_iteration at gmain.c:3869 #34 g_application_run at gapplication.c:2308
Created attachment 1069127 [details] File: backtrace
Created attachment 1069128 [details] File: cgroup
Created attachment 1069129 [details] File: core_backtrace
Created attachment 1069130 [details] File: dso_list
Created attachment 1069131 [details] File: environ
Created attachment 1069132 [details] File: limits
Created attachment 1069133 [details] File: maps
Created attachment 1069134 [details] File: mountinfo
Created attachment 1069135 [details] File: namespaces
Created attachment 1069136 [details] File: open_fds
Created attachment 1069137 [details] File: proc_pid_status
Created attachment 1069138 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.