Red Hat Bugzilla – Bug 1295409
[abrt] file-roller: xfer_data_free(): file-roller killed by SIGSEGV
Last modified: 2016-12-20 12:35:56 EST
Version-Release number of selected component:
cmdline: file-roller --notify --default-dir=sftp://email@example.com/home/liveuser/2TB-disk/game --add sftp://firstname.lastname@example.org/home/liveuser/2TB-disk/game/epsxe1925lin
runlevel: N 5
Thread no. 1 (8 frames)
#2 xfer_data_free at fr-command.c:82
#3 g_copy_current_file at gio-utils.c:833
#4 g_copy_next_file at gio-utils.c:772
#5 g_copy_files_ready_cb at gio-utils.c:806
#6 g_task_return_now at gtask.c:1106
#7 complete_in_idle_cb at gtask.c:1120
#11 g_main_context_iteration at gmain.c:3901
#12 g_application_run at gapplication.c:2311
Potential duplicate: bug 1080426
Created attachment 1111452 [details]
Created attachment 1111453 [details]
Created attachment 1111454 [details]
Created attachment 1111455 [details]
Created attachment 1111456 [details]
Created attachment 1111457 [details]
Created attachment 1111458 [details]
Created attachment 1111459 [details]
Created attachment 1111460 [details]
Created attachment 1111461 [details]
Created attachment 1111462 [details]
Created attachment 1111463 [details]
Created attachment 1111464 [details]
Similar problem has been detected:
I tried to compress some files.
cmdline: file-roller --notify --default-dir=smb://server/public/Administration/XXXXXXXX/DKB/Kontoausz%C3%BCge/XXXXXXXXXXXXX%20-%20Hauptkonto --add smb://server/public/Administration/Peter/XXX/Kontoausz%C3%BCge/XXXXXXXX%20-%20Hauptkonto/Kontoauszug_XXXXXXX_Nr_2014_001_per_2014_01_03.pdf smb://server/public/Administration/Peter/DKB/Kontoausz%C3%BCge/XXXXXXXX%20-%20Hauptkonto/Kontoauszug_XXXXXXXX_Nr_2014_002_per_2014_02_04.pdf smb://server/public/Administration/Peter/DKB/Kontoausz%C3%BCge/XXXXXXXXXX%20-%20Hauptkonto/Kontoauszug_XXXXXXXXXXX_Nr_2014_003_per_2014_03_04.pdf smb://server/public/Administration/Peter/DKB/Kontoausz%C3%BCge/XXXXXXXXXXXX%20-%20Hauptkonto/Kontoauszug_XXXXXXXXX_Nr_2014_004_per_2014_04_02.pdf smb://server/public/Administration/Peter/DKB/Kontoausz%C3%BCge/XXXXXXXXXXX%20-%20Hauptkonto/Kontoauszug_XXXXXXXXXXXX_Nr_2014_005_per_2014_05_02.pdf smb://server/public/Administration/Peter/DKB/Kontoausz%C3%BCge/XXXXXXXXXXXXX%20-%20Hauptkonto/Kontoauszug_XXXXXXXXXXXXXX_Nr_2014_006_per_2014_06_03.pdf smb://server/public/Administration/Peter/DKB/Kontoausz%C3%BCge/XXXXXXXXXXXX%20-%20Hauptkonto/Kontoauszug_XXXXXXXXXXXXXX_Nr_2014_007_per_2014_07_02.pdf smb://server/public/Administration/Peter/DKB/Kontoausz%C3%BCge/XXXXXXXXXX%20-%20Hauptkonto/Kontoauszug_XXXXXXXXXX_Nr_2014_008_per_2014_08_04.pdf
reason: file-roller killed by SIGABRT
runlevel: N 5
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.