Joplin fails to start

Support
1

Operating system

Windows

Joplin version

2.13.12

What issue do you have?

Hi,

Joplin does not start after latest update. It appears in task manager for a moment and then closes. Restart did not help. Windows 11.

2

Which version are you using? Does it work if you download the latest version directly from there? https://joplinapp.org/

3

I downloaded clicking the popup from the app. Downloaded again using the link and surprisingly it worked. Thanks!

Joplin crashes after 30 seconds
4

Happened to me too. It was suggested to allow for automatic updates, get pre-releases and enable auto-updates, but that did not prevent Joplin to close after a few seconds. I have Joplin 3.4.12 installed. The way that seemed to work is to disconnect from Internet, start Joplin and then re-establish internet connection….. For sure not an ideal situation.

5

I am also having a similar issue where Joplin is not starting. Though, I am on Fedora Linux (using the Flatpak (Unofficial?)). I am not sure if this issue is caused by the same thing as the Windows one.

OS

  • Fedora 43 KDE

Joplin Version

  • 3.4.12

Issue

When I click on the Joplin Icon, it bounces up and down like it is trying to launch. It then does not open. The issue also happens with Joplin if I use the official download method.

Temporary Workaround

I have found that it does launch a Joplin process. The process also does not exit automatically — it even appears to persist after a reboot. If I kill the process (killall joplin) and click on the Joplin icon, it exhibits the same problematic behavior. However, if I kill the process, delete the “window-state-prod.json” file from “~/.config/joplin-desktop/”, and then click the Joplin icon, Joplin opens normally. However, sometimes after I close Joplin, I have to redo the “fix” steps mentioned in the previous sentence.

1 Like
7

Upgrading fixed my issue :grinning_face:

8

I am having the same issue on Windows. The log states that the problem is that the updater is not signed by the actual project owner:

Code: ERR_UPDATER_INVALID_SIGNATURE
Error: New version 3.5.11 is not signed by the application owner: publisherNames: Cozic Ltd, raw info: {
  "SignerCertificate": {
    "FriendlyName": "",
    "IssuerName": {
      "Name": "CN=SSL.com Code Signing Intermediate CA RSA R1, O=SSL Corp, L=Houston, S=Texas, C=US",
      "Oid": "System.Security.Cryptography.Oid"
    },
    "NotAfter": "/Date(1854154596000)/",
    "NotBefore": "/Date(1759546596000)/",
    "PrivateKey": null,
    "PublicKey": {
      "Key": "System.Security.Cryptography.RSACryptoServiceProvider",
      "Oid": "System.Security.Cryptography.Oid",
      "EncodedKeyValue": "System.Security.Cryptography.AsnEncodedData",
      "EncodedParameters": "System.Security.Cryptography.AsnEncodedData"
    },
    "SerialNumber": "73CFC43AF68F0F279BDD4C285494F440",
    "SignatureAlgorithm": {
      "Value": "1.2.840.113549.1.1.11",
      "FriendlyName": "sha256RSA"
    },
    "Thumbprint": "AF0C1B9451567F9AF077DD0646D2927153B05DAF",
    "Version": 3,
    "Issuer": "CN=SSL.com Code Signing Intermediate CA RSA R1, O=SSL Corp, L=Houston, S=Texas, C=US",
    "Subject": "CN=Joplin, O=Joplin, L=Nancy, C=FR"
  },

Interestingly enough, downloading the installer from the website also prompts me because of “unverified publisher”, which I don’t remember if this happened when I installed Joplin originally.

With the amount of supply chain attacks going on in javascript-land, I think I’d rather disable automatic updates until there’s official word on what’s happened.

Disabling automatic updates fixes the crash.

9

For reference, I'm linking to two related forum posts: Windows Defender objects to the installer - #3 by laurent, Joplin crashes shortly after launch - #2 by laurent.

10

Thank you for sharing this! Having gone through the exact pain they describe in getting code certificates to get accepted generally in Windows, I understand the issue now. The fix indeed then is to just update to the latest version.

1 Like