Titanium JIRA Archive
Appcelerator Community (AC)

[AC-2262] longjohn.js:184 -- Error: EPERM, operation not permitted

GitHub Issuen/a
TypeBug
Priorityn/a
StatusClosed
ResolutionDuplicate
Resolution Date2014-02-17T16:37:22.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsStudio, Titanium SDK & CLI
Labelsn/a
ReporterRadek Tomecek
AssigneeRitu Agrawal
Created2014-02-17T13:18:33.000+0000
Updated2016-03-08T07:41:16.000+0000

Description

C:\Users\Radek\AppData\Roaming\npm\node_modules\titanium\node_modules\longjohn\dist\longjohn.js:184 throw e; ^ Error: EPERM, operation not permitted 'C:\Program Files\Windows NT\Příslušenství' at fs.readdirSync (fs.js:654:18) at scan (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\titanium-sdk\lib\emulators\genymotion.js:138:25) at scan (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\titanium-sdk\lib\emulators\genymotion.js:150:26) at scan (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\titanium-sdk\lib\emulators\genymotion.js:150:26) at C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\titanium-sdk\lib\emulators\genymotion.js:156:10 at C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\titanium-sdk\lib\emulators\genymotion.js:113:8 at q.process (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:731:21) at processImmediate (timers.js:330:15) --------------------------------------------- at async.setImmediate (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:96:15) at C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:696:21 at Array.forEach (native) at _each (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:32:24) at _insert (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:681:11) at q.push (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:708:15) at C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\titanium-sdk\lib\emulators\genymotion.js:129:12 at queue.drain (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\node-appc\lib\subprocess.js:108:3) --------------------------------------------- at async.setImmediate (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:96:15) at C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:696:21 at Array.forEach (native) at _each (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:32:24) at _insert (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:681:11) at q.push (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\async\lib\async.js:708:15) at Object.findExecutable (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\node-appc\lib\subprocess.js:113:8) at async.parallel.virtualbox (C:\android-sdk-win\mobilesdk\win32\3.2.1.GA\node_modules\titanium-sdk\lib\emulators\genymotion.js:99:20) [ERROR] Application Installer abnormal process termination. Process exit value was 8

Comments

  1. Radek Tomecek 2014-02-17

    And on top of that I am wondering, why the system thread is interested in going into 'C:\Program Files\Windows NT\Příslušenství'
  2. Ritu Agrawal 2014-02-17

    Resolving this ticket as a duplicate of TIMOB-16074. Please track that ticket for further updates.

JSON Source