ferdium-app: Bug: Ferdium only shows blank window

Avoid duplicates

  • I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.0.0.nightly.56.r5506.cf182890-1 (AUR ferdi-git package)

What Operating System are you using?

Other Linux

Operating System Version

Archlinux

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

When starting ferdium, the window should show my services and I should be able to interact with them.

Actual Behavior

After starting (and opening) ferdium, the window remains blank (see screenshot below). I get the following log output:

Steps to reproduce

Launch ferdium

Debug link

Not Possible. The help menu has no entries (show (empty)

Screenshots

Screenshot of the ferdium window, just to make sure we talk about the same thing when I say it remains blank Screenshot_20220611_132620

Additional information

$ ferdium --enable-logging             
[37145:0611/132530.385413:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[37177:0611/132530.411115:WARNING:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[37145:0611/132530.644542:INFO:CONSOLE(111)] "%cDownload the React DevTools for a better development experience: https://reactjs.org/link/react-devtools
You might need to use a local HTTP server (instead of file://): https://reactjs.org/link/react-devtools-faq font-weight:bold", source: /opt/ferdium-git/resources/app.asar/node_modules/@sentry/utils/dist/instrument.js (111)
[37145:0611/132531.169996:INFO:CONSOLE(943)] "Uncaught Error: Cannot find module 'react-virtualized'
Require stack:
- /opt/ferdium-git/resources/app.asar/node_modules/electron-react-titlebar/dist/renderer.js
- /opt/ferdium-git/resources/app.asar/components/layout/AppLayout.js
- /opt/ferdium-git/resources/app.asar/containers/layout/AppLayoutContainer.js
- /opt/ferdium-git/resources/app.asar/routes.js
- /opt/ferdium-git/resources/app.asar/index.html", source: node:internal/modules/cjs/loader (943)
[37145:0611/132532.337313:INFO:CONSOLE(111)] "Could not connect to Sentry main process. Did you call init in the Electron main process?", source: /opt/ferdium-git/resources/app.asar/node_modules/@sentry/utils/dist/instrument.js (111)

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 2
  • Comments: 29 (18 by maintainers)

Most upvoted comments

#236 works for me, too.

I opened an issue for the dependency packaging: https://github.com/KochiyaOcean/electron-react-titlebar/issues/27

If it works for you - please approve the PR?

Cool, thanks! This patch seems to be working for me:

diff --git a/package.json b/package.json
index 0c931c20..492ed74a 100644
--- a/package.json
+++ b/package.json
@@ -70,7 +70,7 @@
     "debug": "4.3.4",
     "electron-dl": "^3.3.1",
     "electron-find": "^1.0.7",
-    "electron-react-titlebar": "^1.1.0",
+    "electron-react-titlebar": "1.1.0",
     "electron-updater": "^4.6.5",
     "electron-window-state": "^5.0.3",
     "fast-folder-size": "^1.6.1",

We shouldn’t need #236 – it doesn’t fix the problem at all, only hides it.

package-lock.json should already lock the dependencies, so we should be instead thinking about how to make sure electron-builder uses that properly.

But this problem is much mysterious: it looks like electron-react-titlebar@1.2.0 has the @1.1.0 bundles in its dist directory! The files in src are correct an reference electron-window, but the bundles are just outdate. I suspect this is a packaging error in electron-react-titlebar and I’ll raise an issue there.

In the meantime, we should lock electron-react-titlebar@1.1.0 with two TODOs:

  • Bump to 1.2.0 when the packaging error is fixed.
  • Try to make electron-builder respect package-lock.json

This is the error I see on my mac with build 57. Uncaught Error: Cannot find module ‘react-virtualized’

Require stack:
- /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/electron-react-titlebar/dist/renderer.js
- /Applications/Ferdium.app/Contents/Resources/app.asar/components/layout/AppLayout.js
- /Applications/Ferdium.app/Contents/Resources/app.asar/containers/layout/AppLayoutContainer.js
- /Applications/Ferdium.app/Contents/Resources/app.asar/routes.js
- /Applications/Ferdium.app/Contents/Resources/app.asar/index.html
    at Module._resolveFilename (node:internal/modules/cjs/loader:940:15)
    at i._resolveFilename (node:electron/js2c/renderer_init:33:1095)
    at Module._load (node:internal/modules/cjs/loader:785:27)
    at c._load (node:electron/js2c/asar_bundle:5:13343)
    at i._load (node:electron/js2c/renderer_init:33:356)
    at Module.require (node:internal/modules/cjs/loader:1012:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at menu-list-item.tsx:4:108
    at Object.<anonymous> (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/electron-react-titlebar/dist/renderer.js:1:8591)
    at Object.<anonymous> (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/electron-react-titlebar/dist/renderer.js:3:3)```

node:internal/modules/cjs/loader:943 

Downloaded the built binaries from GH, nightly 56 works, while nightly 57 doesn’t - tested on my mac.

#235 signals the same problem on Manjaro and W11.

no, unfortunately not. I am currently trying to find the responsible commit, but given my very limited experience with npm, this might take a while