When I update tabby 1.0.148 to 1.01.149 and I can't use this app anymore.

[TheSonder]

I'm using window10 system, when I try to overwrite from version 1.0.148 to install the updated version 1.0.149, I can't open the tabby software, and after deleting the software, deleting the registry no matter install 1.0.148 or 1.0.149 does not work, still can't open.

[Eugeny]

Please try deleting everything except config.json in your %APPDATA%/Tabby folder.

[miltlima]

Hello folks, I have the same problem, but I use Linux !

[Eugeny]

@miltlima on Linux, it's ~/.config/tabby

[EvilExecutor]

I'm experiencing the same issue, tried following the below steps but still it won't open.

Please try deleting everything except config.json in your %APPDATA%/Tabby folder.

[Eugeny]

OK - this next step requires a bit more work:

• Start Tabby with the --inspect flag - i.e. tabby --inspect (or tabby.exe --inspect on Windows) from another terminal.
• Note the port that is logged in the console (9229 by default).
• Open Chrome and navigate to chrome://inspect
• Add 127.0.0.1:port to "Network targets"
• Tabby should show up in Remote Targets
• Click "inspect" on it
• Look for errors in the Console tab

[TheSonder]

OK - this next step requires a bit more work:

• Start Tabby with the --inspect flag - i.e. tabby --inspect (or tabby.exe --inspect on Windows) from another terminal.
• Note the port that is logged in the console (9229 by default).
• Open Chrome and navigate to chrome://inspect
• Add 127.0.0.1:port to "Network targets"
• Tabby should show up in Remote Targets
• Click "inspect" on it
• Look for errors in the Console tab

Thank you very much, I have solved the problem as you said.

[Eugeny]

Uhh how did you solve it? Did Tabby "just" start with --inspect?

[cliope]

OK - this next step requires a bit more work:

• Start Tabby with the --inspect flag - i.e. tabby --inspect (or tabby.exe --inspect on Windows) from another terminal.
• Note the port that is logged in the console (9229 by default).
• Open Chrome and navigate to chrome://inspect
• Add 127.0.0.1:port to "Network targets"
• Tabby should show up in Remote Targets
• Click "inspect" on it
• Look for errors in the Console tab

Hi, I followed these steps and ended up with the following errors. I noticed that there ARE running tabby instances at backstage, since when I tried to re-install tabby, my security software tells me that the installation process is trying to kill running tabby instances.

DevTools failed to load source map: Could not load content for file:///C:/Program%20Files/Tabby/resources/app.asar/dist/main.js.map: System error: net::ERR_FILE_NOT_FOUND
DevTools failed to load source map: Could not load content for file:///C:/Program%20Files/Tabby/resources/app.asar/node_modules/node-pty/lib/index.js.map: System error: net::ERR_FILE_NOT_FOUND
DevTools failed to load source map: Could not load content for file:///C:/Program%20Files/Tabby/resources/app.asar/node_modules/node-pty/lib/windowsTerminal.js.map: System error: net::ERR_FILE_NOT_FOUND
DevTools failed to load source map: Could not load content for file:///C:/Program%20Files/Tabby/resources/app.asar/node_modules/node-pty/lib/terminal.js.map: System error: net::ERR_FILE_NOT_FOUND
DevTools failed to load source map: Could not load content for file:///C:/Program%20Files/Tabby/resources/app.asar/node_modules/node-pty/lib/eventEmitter2.js.map: System error: net::ERR_FILE_NOT_FOUND
DevTools failed to load source map: Could not load content for file:///C:/Program%20Files/Tabby/resources/app.asar/node_modules/node-pty/lib/windowsPtyAgent.js.map: System error: net::ERR_FILE_NOT_FOUND
DevTools failed to load source map: Could not load content for file:///C:/Program%20Files/Tabby/resources/app.asar/node_modules/node-pty/lib/utils.js.map: System error: net::ERR_FILE_NOT_FOUND

[Eugeny]

Oh, so it was killing those instances that allowed you to start it again?

[Eugeny]

Found it - for some reason, the config file ends up empty. I've taken down the release and am investigating this. To get the app to work again, delete the empty config.json file.

[Eugeny]

Apparently there's a race condition - when the Settings tab is active when Tabby is being closed, it will try to save the config file (the Settings tab does this when closed) and the process ending.

[Eugeny]

Fixed nightly build: https://github.com/Eugeny/tabby/actions/runs/1085177985

GitHub

fixed config file getting spontaneously erased - fixes #4293 · Eugeny/tabby@8b8bacd

A terminal for a more modern age (formerly Terminus) - fixed config file getting spontaneously erased - fixes #4293 · 8b8bacd

[TheSonder]

Uhh how did you solve it? Did Tabby "just" start with --inspect?

No,I just delete all the things the tabby created.