Edex-ui: Can't Change Terminal Emulator

[SkeleBones]

Technical information

Using version:

• [x] master (running from GitHub-published source code, currently v3.0.0-pre)
• [ ] latest (latest release, currently v2.2.2)
• [ ] vX.X.X (specify other version)

Running on:

• [ ] Linux
• [x] Windows
• [ ] macOS

How comfortable you are with your system and/or IT in general:

• [x] I'm kind of lost, honestly
• [ ] I know what's up, I could help you run some commands or checks
• [ ] My machine is fully under my control, tell me what you need
• [ ] I attended Defcon last year

---

Problem

If I change the shell and restart the terminal, it refuses to launch. If I change it back it doesn't start either. The only way I can start it again after changing it is to delete the settings.json file.

[AkechiShiro]

I haven't encountered this issue when changing the shell from bash to zsh for instance. What is the shell emulator you're trying to set in the settings.json ?
Also I take it you have bash installed ?

[SkeleBones]

I have bash installed. I am trying to use PowerShell 7-preview. It is installed in the normal place.

[AkechiShiro]

I'd like to know from what kind of environnement are you trying to launch the terminal is ? Is an X11 server launched ? Or are you trying to launch the terminal in a TTY ?

If you're trying from a TTY then that explains the problem.

[SkeleBones]

I'm using X11.

[SkeleBones]

Another thing is it does sort of launch. It just doesn't open fully. I can see it running in the task manager but it never starts the UI. This is after I've tried to change the shell.

[GitSquared]

What version? (of edex)

[SkeleBones]

v2.2.2

[parkerlreed]

https://github.com/GitSquared/edex-ui/issues/769

Should I submit a new issue?
It depends. As mentioned above, any comeback to this project would start with a code rewrite, effectively eliminating all current bugs (and surely creating new ones, but that's another story).
If you're on v2.2.2, the latest released version, chances are your problem is fixed in the never-released v3.0. To access it, you'll have to build from source.
If you're on v3, please submit an issue, but beware that I might not get back to you in a timely manner.

[SkeleBones]

Same issue on v3.

[SkeleBones]

Also, I seemed to have formated this Bug Report wrong.

[GitSquared]

Also, I seemed to have formated this Bug Report wrong.

It's fine, however as you probably guessed if you looked over at #769 i might not get back to you anytime soon, sorry. Off the top of my head i can't figure out what's happening here.

[SkeleBones]

Yeah, it is fine. I can just use the stock shell for now.

[AkechiShiro]

Does the stock shell work ? I could try to install the Powershell preview 7 on my distro and give it a try to see if I can reproduce your issue.

[SkeleBones]

Yeah, stock works until I change it then I have to delete settings.json to fix it. I am not able to change it back.

[SkeleBones]

Didn't mean to do that.

[SkeleBones]

Semi Log

(node:13784) UnhandledPromiseRejectionWarning: Error: File not found: C:\Program
at new WindowsPtyAgent (C:\edex-ui\src\node_modules\node-pty\lib\windowsPtyAgent.js:74:36)
at new WindowsTerminal (C:\edex-ui\src\node_modules\node-pty\lib\windowsTerminal.js:49:24)
at Object.spawn (C:\edex-ui\src\node_modules\node-pty\lib\index.js:28:12)
at new Terminal (C:\edex-ui\src\classes\terminal.class.js:404:33)
at App. (C:\edex-ui\src_boot.js:234:11)
(node:13784) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:13784) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[bleek42]

Just wanted to chime in and say @SkeleBones is not alone. I just discovered eDEX-UI today and having problems changing the default shell. Using Windows 10 and trying to change settings.json from the default Powershell to Bash.

[GitSquared]

Possibly related: #740 #698

[SkeleBones]

I tried what it said in #698, it didn't work. I'll have to check #740.

[rozbrajaczpoziomow]

I think I know what's going on,

(node:13784) UnhandledPromiseRejectionWarning: Error: File not found: C:\Program [...]

I think when you're trying to call powershell, you're trying to do smth like this:
start C:\Program Files...
But its not quoted... And then windows thinks (I think it thinks that way) like "C:\Program" is the path and "Files..." is the argument.

[bleek42]

I think I know what's going on,

(node:13784) UnhandledPromiseRejectionWarning: Error: File not found: C:\Program [...]

I think when you're trying to call powershell, you're trying to do smth like this:
start C:\Program Files...
But its not quoted... And then windows thinks (I think it thinks that way) like "C:\Program" is the path and "Files..." is the argument.

soooo in settings.json, right.... in the default terminal, where it now just says powershell.exe, instead of changing it to simply bash.exe, I change it to the entire path where bash.exe is actually located..? still get the same problem. I save these new settings and restart eDEX, and the program just does not start.

[rozbrajaczpoziomow]

I think I know what's going on,

(node:13784) UnhandledPromiseRejectionWarning: Error: File not found: C:\Program [...]

I think when you're trying to call powershell, you're trying to do smth like this:
start C:\Program Files...
But its not quoted... And then windows thinks (I think it thinks that way) like "C:\Program" is the path and "Files..." is the argument.

soooo in settings.json, right.... in the default terminal, where it now just says powershell.exe, instead of changing it to simply bash.exe, I change it to the entire path where bash.exe is actually located..? still get the same problem. I save these new settings and restart eDEX, and the program just does not start.

I don't think it's an issue with your settings.json file, but propably how the TTY is started? Not really sure, because I don't know how it's handled, but maybe I'll try to look into the source code and figure it out.

Edit: so I looked at:
src/_boot.js:236
src/classes/terminal.class.js:404

It seems like it splits the path to TTY to spaces and then takes the first element of it, so there should be no problems with arguments, but idk how xTerm in Electron works, so im kinda lost, but this also may have been fixed because of (another issue I read but i don't remember the # of it) on the unreleased 3.0 version.

[Animus-Surge]

I’ll have a look. Seems like reading paths from the settings.json messed up if there’s any spaces in it.