Exception on ctrl+c

Bug #288742 reported by Kamil Páral
2
Affects Status Importance Assigned to Milestone
fiDefrag
New
Critical
Unassigned

Bug Description

FiDefrag 2.11, Ubuntu 8.04.

This is what happened when I wanted to cancel the defragmentation and hit Ctrl+c:

$ fidefrag -d .

=== Defragmenting . - 1,4G - 8 Files - 5 Passes ===

=== Building File List...

--- Pass 1 / 5 ---

 495.86 MB 23084 P 46.55 P/MB ./The Power Of Nightmares - 02... Phantom Victory.avi
        --> Improved: 23084.00 P --> 1382.00 P
 344.23 MB 13368 P 38.83 P/MB ./The Power Of Nightmares - 01...Its Cold Outside.avi
        --> Improved: 13368.00 P --> 6631.00 P
 492.43 MB 19911 P 40.43 P/MB ./The Power Of Nightmares - 03...dows In The Cave.avi
Traceback (most recent call last):
  File "/home/ripper/různé/compile/fidefrag/src/fidefrag.py", line 62, in <module>
    libfidefrag.defrag_op()
  File "/home/ripper/různé/compile/fidefrag/src/libfidefrag.py", line 244, in defrag_op
    defrag(mf)
  File "/home/ripper/různé/compile/fidefrag/src/libfidefrag.py", line 142, in defrag
    copy = subprocess.Popen(["rsync", "-a", mfile.file, defragdir], stdout = subprocess.PIPE).communicate()[0]
  File "/usr/lib/python2.5/subprocess.py", line 662, in communicate
    stdout = self._fo_read_no_intr(self.stdout)
  File "/usr/lib/python2.5/subprocess.py", line 1019, in _fo_read_no_intr
    return obj.read()
KeyboardInterrupt
$ rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(271) [sender=2.6.9]
$

Fortunatelly the file does not seem to be corrupted. Anyhow the ctrl+c should work flawlessly, it is normal way to cancel program.

Changed in fidefrag:
importance: Undecided → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.