Bug 541895 - System "hangs" while curlftpfs works
Summary: System "hangs" while curlftpfs works
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: curlftpfs
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pavel Alexeev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-27 13:52 UTC by Andrea
Modified: 2010-06-28 15:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 15:30:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andrea 2009-11-27 13:52:50 UTC
Description of problem:

I've mounted an ftp fs via curlftpfs.
Then in a terminal inside Konsole I copy a file using cp.
While the file is being copied, the whole Konsole is frozen, not just the terminal running cp, but as well all other tab in the same console.

Same happens if I copy the file with dolphin. While the file is being copied, dolphin is frozen.

Version-Release number of selected component (if applicable):

curlftpfs-0.9.1-4.fc11.i586

How reproducible:

Always

Steps to Reproduce:
1. mount via curlftpfs
2. copy a large file
3. the application copying the file is frozen
  
Actual results:

Application is frozen, while curlftpfs runs.

Expected results:

Same as any other filesystem.

Additional info:

Comment 1 David Anderson 2009-12-16 13:19:45 UTC
Hi,

Sorry to be slow in responding. My plan is to update to the latest version - 0.9.2, and we hope that'll fix it.

David

Comment 2 David Anderson 2010-01-11 11:31:45 UTC
Hi,

I'm sorry about this. I can't find the time to do this nowadays. I originally packaged this package because I wanted to use it, and wanted to give something back to Fedora - but because I can't make the time it's not helpful for me to maintain it any more. I've orphaned the package, and hopefully a new maintainer will pick it up soon and get this fixed.

Thanks for your patience,
David

Comment 3 Pavel Alexeev 2010-01-12 14:51:04 UTC
Please try new version - http://koji.fedoraproject.org/koji/taskinfo?taskID=1916662

If it helps, I'll post updates.

Comment 4 Bug Zapper 2010-04-28 11:27:08 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 WONTFIX if it remains open with a Fedora 
'version' of '11'.

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 prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-06-28 15:30:45 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.