Description of problem: What I do know is that there is a lot of data to back up so I left it running overnight. When I checked in the morning, it wasn't running. Also, I was backing up to an NFS share. Version-Release number of selected component: grsync-1.2.4-2.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: grsync -i crash_function: g_malloc0 executable: /usr/bin/grsync kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_malloc0 at gmem.c:134 #3 gtk_mark_segment_new at gtktextmark.c:337 #4 gtk_text_mark_init at gtktextmark.c:106 #5 g_type_create_instance at gtype.c:1868 #6 g_object_new_internal at gobject.c:1746 #7 g_object_new_valist at gobject.c:2002 #9 gtk_text_mark_new at gtktextmark.c:212 #10 real_set_mark at gtktextbtree.c:2782 #11 _gtk_text_btree_set_mark at gtktextbtree.c:2830 #12 gtk_text_buffer_set_mark at gtktextbuffer.c:2045
Created attachment 888136 [details] File: backtrace
Created attachment 888137 [details] File: cgroup
Created attachment 888138 [details] File: core_backtrace
Created attachment 888139 [details] File: dso_list
Created attachment 888140 [details] File: environ
Created attachment 888141 [details] File: exploitable
Created attachment 888142 [details] File: limits
Created attachment 888143 [details] File: maps
Created attachment 888144 [details] File: open_fds
Created attachment 888145 [details] File: proc_pid_status
Created attachment 888146 [details] File: var_log_messages
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.