Closed Bug 913663 Opened 12 years ago Closed 9 years ago

XPCOM file moveTo on OS X

Categories

(Core Graveyard :: Embedding: GRE Core, defect)

23 Branch
x86_64
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: info, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release) Build ID: 20130803192641 Steps to reproduce: I am trying to rename a file on OS X a file with the moveTo functionality of XPCOM. The code I am using: var file = Cc["@mozilla.org/file/local;1"].createInstance(Ci.nsIFile); file.initWithPath(filePath); var targetDir = "/somedir/anotherdir"; var targetFileName = "somefilename.txt"; var targetDirFile = Cc["@mozilla.org/file/local;1"].createInstance(Ci.nsIFile); targetDirFile.initWithPath(targetDir); file.moveTo(targetDirFile,targetFileName); The same code works fine on windows and ubuntu linux. Actual results: Error: tagspaces: Renaming failed [Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIFile.initWithPath]" nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location: "JS frame :: resource://gre/modules/XPIProvider.jsm -> file:///Users/___/Library/Application%20Support/Firefox/Profiles/hrodvt51.default/extensions/jid1-FBaMKxTifTSahQ@jetpack/bootstrap.js -> resource://gre/modules/commonjs/toolkit/loader.js -> resource://jid1-fbamkxtiftsahq-at-jetpack/tagspaces/lib/ioutils.js :: rename :: line 331" data: no] Expected results: the moveTo should have renamed the file.
Severity: normal → major
Component: Untriaged → Embedding: GRE Core
Product: Firefox → Core
OS: Linux → Mac OS X
Mass change of bugs in the "Embedding: GRE Core" component in preparation for archiving it. I believe that these are no longer relevant; but if they are, they should be reopened and moved into a component relevant to the code in question.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.