Unable to launch on Ubuntu

[ir-g]

I'm on Ubuntu 16.04 LTS, and when I attempt to launch tide, the application appears to start launching(appears in app dock on left), and then disappears. While, this works well for me on Windows, it is frustrating that this sint working for me on Linux. Are there any know helpers/solutions to this problem?

[joerick]

Hey ir-g, I've not heard of this one before. Sounds like it's crashing before it has a chance to boot up. Would you be able to get some logs of the crash somehow? Perhaps you could start Tide from a terminal window?

[ir-g]

I haven't figured out how to start Tide from the terminal window, though for some days have been trying. Where abouts would the executable be located once installed in Ubuntu/Debian?

…

On Fri, 20 Jan 2017, 11:17 Joe Rickerby, ***@***.***> wrote: Hey ir-g, I've not heard of this one before. Sounds like it's crashing before it has a chance to boot up. Would you be able to get some logs of the crash somehow? Perhaps you could start Tide from a terminal window? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#67 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABHw6HNVULk8b7u60gSPlnxVvaYRyEw9ks5rUJflgaJpZM4LpJYJ> .

[joerick]

I don't know, I'm not really a Linux guy!

Any Ubuntu users please chime in!

[ir-g]

I've just mangaged to find where tide is installed for me: /opt/Tide.
Location of tide was found via dpkg -L tide.

When running, I get:

module.js:442
    throw err;
    ^

Error: Cannot find module '/opt/Tide/resources/electron.asar/browser/init.js'
    at Function.Module._resolveFilename (module.js:440:15)
    at Function.Module._load (module.js:388:25)
    at Module.runMain (module.js:575:10)
    at run (bootstrap_node.js:360:7)
    at startup (bootstrap_node.js:152:9)
    at bootstrap_node.js:479:3

This is because the /opt/Tide/resources directory requires Sudo(admin) access to Read/Write/etc to. As a brute force solution. I did the following.

cd /opt/Tide
sudo chmod -R 777 resources/

This makes the /opt/Tide/resources readable and writeable to anyone. More fine-tuned permissions should be used in any realistic scenario, but that was the source of the issue.

[chrisbeardy]

@ir-g I had the same issue here, your solution worked for me too.