Description of problem: grsync running as root via kdesu to xfer many many many thousands of files in 1.7TB across systems. It ran for about 5 days. I was reviewing the 'completed with errors' report to find the 'permission denied' files I needed to manually xfer. It was a very long listing and I chose to right-click/Select All and copy to clipboard, then paste to kate. Of course the damned thing crashed then, and there doesn't appear to be any log of the report. The trace even complains that '/usr/bin/grsync appears to be deleted' which is not true. The file absolutely still exists in /usr/bin. At this point my only recourse appears to be to run grsync again and let it take several days to discover the permission-problem files so I can repeat the process. Which sux huge. Also, as this is a new system only just configured, it does not have much in the way of debuginfo files, so this report is likely useless. At one time anaconda allowed one to spend the necessary time up front during initial install to make sure everything you wanted on the system -- including debuginfo and devel package groups -- was installed all at the same time, during initial install. No more. The current choices for software installation during initial install are so restricted as to be laughable. Version-Release number of selected component: grsync-1.2.4-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/grsync -i crash_function: handle_error executable: /usr/bin/grsync kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #4 handle_error at xcb_io.c:213 #5 handle_response at xcb_io.c:325 #7 XQueryPointer at QuPntr.c:48 #8 gdk_window_x11_get_pointer at gdkwindow-x11.c:3213 #9 gdk_window_real_window_get_pointer at gdkdisplay.c:568 #10 gdk_window_get_pointer at gdkwindow.c:6526 #11 gdk_device_get_state at gdkinput-x11.c:907 #12 gdk_event_request_motions at gdkevents.c:954 #13 _gtk_tooltip_handle_event at gtktooltip.c:1632 #14 gtk_main_do_event at gtkmain.c:1727
Created attachment 900404 [details] File: backtrace
Created attachment 900405 [details] File: cgroup
Created attachment 900406 [details] File: core_backtrace
Created attachment 900407 [details] File: dso_list
Created attachment 900408 [details] File: environ
Created attachment 900409 [details] File: limits
Created attachment 900410 [details] File: maps
Created attachment 900411 [details] File: open_fds
Created attachment 900412 [details] File: proc_pid_status
Created attachment 900413 [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.