Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

start fails with EPERM

See original GitHub issue

My work computer (Windows 10) bluescreened when connected to a new monitor (yay, Windows) and since then extraterm has failed to start.

Attempting to run extraterm fails immediately with a MessageBox tating:

A JavaScript error occurred in the main process Uncaught exception: Error: EPERM: operation not permitted, open C:\users<name>\AppData\Roaming\extraterm\extraterm.log at Object.fs.openSync (fs.js:646:18) (etc)

The named directory did not exist - in fact virtually nothing under AppData\Roaming at all.

I created the directory for extraterm but the same thing happens.

I created an empty extraterm.log file and that also did nothing.

I can try uninstalling… but that seems heavy handed.

Anyone else seen or solved this problem? Thanks!

Issue Analytics

State:
Created 5 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

hjesscommented, Jan 3, 2019

@sedwards2009 first: thanks for a great emulator!

Despite the fact that this issue is closed, I have a similar problem:

I’ve got an Extraterm icon on my desktop (windows, alas)
Clicking on the icon starts Extraterm
Attempts to start another Extraterm instance fails

I think the failure is because of an attempt to unlink and open an existing logfile. This probably works fine on Unix-like systems (Linux, MacOS), but fails on Windows. Sad.

0reactions

st0lecommented, May 22, 2019

I noticed the C:\Users<username>\AppData\Roaming\extraterm\ folder was readonly. Remove the readonly flag (you might need admin rights)

This resolved the issue for me