Created attachment 363564 [details]
Backtrace from file-roller crash on extract to sftp
This may be related to bug 518510. A backtrace is attached to help determine if that's the case.
I opened a .zip file, navigated down several subfolders, then right-clicked on the single file inside and chose "Extract...". I then chose a mounted sftp location for the extraction point (and didn't change any of the default options for extraction).
I've asked Tomas to take a look at this.
Tomas, any update on this ?
Finally found the root issue - file-roller relies too much on gvfs fuse daemon, getting NULL local paths if not running. As long as it spawns external commands, this is understandable. Have to talk to file-roller developers how to handle this situation best, probably by disabling this functionality or by extracting to local temporary place and transferring to remote afterwards.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
file-roller-2.28.2-3.fc12 has been submitted as an update for Fedora 12.
file-roller-188.8.131.52-3.fc13 has been submitted as an update for Fedora 13.
file-roller-184.108.40.206-3.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update file-roller'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/file-roller-220.127.116.11-3.fc13
file-roller-18.104.22.168-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.