caprine does not start after deleting configuration

[Piscium]

I run Caprine in two PCs using Arch, I am using the dark theme:

• old, ASUS mother board with Nvidia card
• newer, Dell with embedded Intel graphics

I am running Caprine v. 2.35 in the newer PC, Electron v. 6.0.1.

Caprine freezes in both, however far more often in the newer PC. So today I deleted the Caprine configuration in the newer PC (in ~/.config/Caprine) to see if that would solve the problem but it got worse, now Caprine does not start at all. I reinstalled it but did not make any difference. Starting from a terminal this is what I get:

---

$ caprine
(node:7188) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'x' of undefined
at createMainWindow (/usr/lib/caprine/dist-js/index.js:190:28)
at /usr/lib/caprine/dist-js/index.js:240:18
(node:7188) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'x' of undefined
at createMainWindow (/usr/lib/caprine/dist-js/index.js:190:28)
at /usr/lib/caprine/dist-js/index.js:240:18
(node:7188) 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:7188) 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:7188) [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.
(node:7188) [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.

[whitecrownclown]

@Piscium This issue has been fixed and will be in a future release (#1037).

Until then you can use v2.34 or v2.36 (they're basically the same) to avoid this issue.

[Piscium]

Yes, I downgraded back to 2.34 and the problem disappeared. However the original issue of the freeze is still there. I will close this issue and create a new one about the freeze.