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

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)
#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:
We shouldn’t need #236 – it doesn’t fix the problem at all, only hides it.
package-lock.jsonshould already lock the dependencies, so we should be instead thinking about how to make sureelectron-builderuses that properly.But this problem is much mysterious: it looks like
electron-react-titlebar@1.2.0has the@1.1.0bundles in itsdistdirectory! The files insrcare correct an referenceelectron-window, but the bundles are just outdate. I suspect this is a packaging error inelectron-react-titlebarand I’ll raise an issue there.In the meantime, we should lock
electron-react-titlebar@1.1.0with two TODOs:electron-builderrespectpackage-lock.jsonThis is the error I see on my mac with build 57. Uncaught Error: Cannot find module ‘react-virtualized’
Downloaded the built binaries from GH,
nightly 56works, whilenightly 57doesn’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