error Couldn't open "path-to-file.part": Permission denied

Bug #707674 reported by Phil Colbourn on 2011-01-25

This bug report was converted into a question: question #143042: error Couldn't open "path-to-file.part": Permission denied.

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: transmission

When this error happens, Transmission Pauses all activity.
It is followed by these two messages:

error Couldn't open "path-to-file.part": Permission denied
error <torrent> tr_fdFileCheckout failed for "path-to-file.part": Permission denied
<torrent> Pausing

I tried un-ticking this file so that it would not be downloaded, but the error eventually happened again - about 7 hours later - which is better than normal where if fails after a few minutes.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: transmission-gtk 2.05-0ubuntu0.1
ProcVersionSignature: Ubuntu 2.6.35-25.43-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Wed Jan 26 08:54:32 2011
ExecutablePath: /usr/bin/transmission
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
SourcePackage: transmission

Phil Colbourn (philcolbourn) wrote :
Phil Colbourn (philcolbourn) wrote :

I have since deleted the offending file, forced a verify and all is well so far. Nautilus showed a padlock indicating that the permissions were wrong - how would that happen?

Unfortunately, in my enthusiasm in locating the probably cause of the fault, I deleted it without checking the permissions.

Phil Colbourn (philcolbourn) wrote :

All seems ok.

I suspect the file's permissions were the real cause.

Only one file had incorrect permissions. I suspect/guess that I may have started Transmission as root for a few seconds, and this must have been the file that was created during that time.

But, could the program continue to work on other files and provide a warning instead of stopping?

Phil Colbourn (philcolbourn) wrote :

Problem resolved and not a bug. But I asked whether the error handling behavior could be changed.

Changed in transmission (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions