Bug 1080426

Summary: [abrt] file-roller: xfer_data_free(): file-roller killed by SIGABRT
Product: [Fedora] Fedora Reporter: sebastian.frenger
Component: file-rollerAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: mclasen, musuruan, pichot.malo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b3e3a4216e6eab7a96fa01314a339ff5c04e108a
Whiteboard: abrt_hash:55c684331e9017b39d2398dbd6677628cd6e5a7c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:41:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description sebastian.frenger 2014-03-25 12:26:34 UTC
Description of problem:
Compressing on a network share onto a network share

Version-Release number of selected component:
file-roller-3.10.2.1-1.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        file-roller --notify --default-dir=smb://192.168.0.25/qplatte/sebastianf --add smb://192.168.0.25/qplatte/sebastianf/gflAnwenderschulung
crash_function: xfer_data_free
executable:     /usr/bin/file-roller
kernel:         3.13.6-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #6 xfer_data_free at fr-command.c:82
 #7 g_copy_current_file at gio-utils.c:833
 #8 g_copy_next_file at gio-utils.c:772
 #9 g_copy_files_ready_cb at gio-utils.c:806
 #10 g_task_return_now at gtask.c:1108
 #11 complete_in_idle_cb at gtask.c:1117
 #15 g_main_context_iteration at gmain.c:3774
 #16 g_application_run at gapplication.c:1635

Potential duplicate: bug 910789

Comment 1 sebastian.frenger 2014-03-25 12:26:38 UTC
Created attachment 878437 [details]
File: backtrace

Comment 2 sebastian.frenger 2014-03-25 12:26:40 UTC
Created attachment 878438 [details]
File: cgroup

Comment 3 sebastian.frenger 2014-03-25 12:26:43 UTC
Created attachment 878439 [details]
File: core_backtrace

Comment 4 sebastian.frenger 2014-03-25 12:26:45 UTC
Created attachment 878440 [details]
File: dso_list

Comment 5 sebastian.frenger 2014-03-25 12:26:53 UTC
Created attachment 878441 [details]
File: environ

Comment 6 sebastian.frenger 2014-03-25 12:26:57 UTC
Created attachment 878442 [details]
File: limits

Comment 7 sebastian.frenger 2014-03-25 12:26:59 UTC
Created attachment 878443 [details]
File: maps

Comment 8 sebastian.frenger 2014-03-25 12:27:01 UTC
Created attachment 878444 [details]
File: open_fds

Comment 9 sebastian.frenger 2014-03-25 12:27:04 UTC
Created attachment 878445 [details]
File: proc_pid_status

Comment 10 sebastian.frenger 2014-03-25 12:27:06 UTC
Created attachment 878446 [details]
File: var_log_messages

Comment 11 Andrea Musuruane 2014-08-13 08:48:12 UTC
Another user experienced a similar problem:

Can't create a ZIP archive with files taken from an external NAS unit.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        file-roller --notify --default-dir=smb://192.168.1.203/multimedia/Photos/2014_06_02%20(Festa%20della%20Repubblica%20-%20Foto%20Michele) --add smb://192.168.1.203/multimedia/Photos/2014_06_02%20(Festa%20della%20Repubblica%20-%20Foto%20Michele)/02-06-230840-6972.JPG smb://192.168.1.203/multimedia/Photos/2014_06_02%20(Festa%20della%20Repubblica%20-%20Foto%20Michele)/02-06-230852-6973.JPG smb://192.168.1.203/multimedia/Photos/2014_06_02%20(Festa%20della%20Repubblica%20-%20Foto%20Michele)/02-06-231048-6974.JPG smb://192.168.1.203/multimedia/Photos/2014_06_02%20(Festa%20della%20Repubblica%20-%20Foto%20Michele)/02-06-231102-6975.JPG
crash_function: xfer_data_free
executable:     /usr/bin/file-roller
kernel:         3.15.8-200.fc20.x86_64
package:        file-roller-3.10.2.1-1.fc20
reason:         file-roller killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 12 Fedora End Of Life 2015-05-29 11:21:46 UTC
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.

Comment 13 Fedora End Of Life 2015-06-29 19:41:32 UTC
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.