Signal-desktop: App doesn't start anymore (1.15.0-Beta.7)

[Le1b1]

[x] I have searched open and closed issues for duplicates

---

Bug description

Signal-Desktop doesn't start anymore.

Terminal output:

A JavaScript error occurred in the main process
Uncaught Exception:
Error: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:172:20)
    at Object.Module._extensions..node (module.js:671:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:186:18)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:504:12)
    at Function.Module._load (module.js:496:3)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/opt/Signal Beta/resources/app.asar/node_modules/@journeyapps/sqlcipher/lib/sqlite3.js:4:15)
    at Object.<anonymous> (/opt/Signal Beta/resources/app.asar/node_modules/@journeyapps/sqlcipher/lib/sqlite3.js:190:3)

Steps to reproduce

1. Start Signal-Desktop

Actual result:

See above

Expected result:

Signal-Desktop starts

Platform info

Signal version:

1.15.0.Beta.7

Operating System:

Debian-9

Linked device version:

4.24.5

Link to debug log

Not possible

[Le1b1]

Possible hint:
Debian-9 provides only libssl1.0.2 with libcrypto.so.1.0.2.

[scottnonnenberg-signal]

This should be fixed in the next beta release, which will come out today. Please let us know if that fixes it for you!

[scottnonnenberg-signal]

This should be fixed in this release: https://github.com/signalapp/Signal-Desktop/releases/tag/v1.15.0-beta.8

[Le1b1]

Nope, launch fails with the same output.

[rnyn]

I'm getting terminal output "Uncaught error or unhandled promise rejection: Error: SQLITE_NOTADB: file is not a database"
then hangs, when trying to run the latest beta release signal desktop in Ubuntu 18.04. previous release also was not launching.

[scottnonnenberg-signal]

@rnyn When you get that error message, the SQLCipher decryption key is incorrect. Can you talk about the history of Signal Desktop on that machine? Had it started migrating messages over?

[linux4life798]

Just to reinforce @Le1b1 's original issue. We still seem to have an issue with finding libcrypto.so. Even with beta.8, I get the following error:

A JavaScript error occurred in the main process
Uncaught Exception:
Error: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:172:20)
    at Object.Module._extensions..node (module.js:671:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:186:18)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:504:12)
    at Function.Module._load (module.js:496:3)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/opt/Signal Beta/resources/app.asar/node_modules/@journeyapps/sqlcipher/lib/sqlite3.js:4:15)
    at Object.<anonymous> (/opt/Signal Beta/resources/app.asar/node_modules/@journeyapps/sqlcipher/lib/sqlite3.js:190:3)

I currently have the following ssl packages installed:

ii  libssl-dev:amd64                       1.1.0h-4                                amd64        Secure Sockets Layer toolkit - development files
ii  libssl-doc                             1.1.0h-4                                all          Secure Sockets Layer toolkit - development documentation
ii  libssl1.0.2:amd64                      1.0.2o-1                                amd64        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.1:amd64                        1.1.0h-4                                amd64        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.1:i386                         1.1.0h-4                                i386         Secure Sockets Layer toolkit - shared libraries

[Le1b1]

1.15.0-Beta.9 fixed it for me.
Thanks @scottnonnenberg-signal

[Le1b1]

@unDocUMeantIt No, yours is not the same issue. This one was about the missing 'ibcrypto.so.1.0.0'.
Please open another issue (if there isn't already one).