lens
lens copied to clipboard
lensapp
Lens does not run on Fedora 35
Describe the bug After upgrading from Fedora 34 to 35 Lens does not run anymore.
To Reproduce Steps to reproduce the behavior:
- Try to launch Lens
Expected behavior Lens showing up
Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
- Lens Version: lens-5.2.6_latest.20211104.1-20211104.1.x86_64
- OS: Fedora 35
- Installation method (e.g. snap or AppImage in Linux): RPM for x86_64
Logs: When you run the application executable from command line you will see some logging output. Please paste them here:
/opt/Lens/lens
info: ▪ 📟 Setting Lens as protocol client for lens:// +0ms
info: ▪ 📟 Protocol client register failed ❗ +8ms
info: ▪ 🚀 Starting Lens from "/opt/Lens/lens" +40ms
info: ▪ 🐚 Syncing shell environment +0ms
info: ▪ 💾 Loading stores +140ms
info: ▪ [DS]: LOADED from /home/mastag/.config/Lens/lens-user-store.json +10ms
info: ▪ [NA]: LOADED from /home/mastag/.config/Lens/lens-cluster-store.json +36ms
info: ▪ [IU]: LOADED from /home/mastag/.config/Lens/lens-hotbar-store.json +2ms
info: ▪ [MT]: LOADED from /home/mastag/.config/Lens/lens-extensions.json +0ms
info: ▪ [EC]: LOADED from /home/mastag/.config/Lens/lens-filesystem-provisioner-store.json +1ms
info: ▪ [FA]: LOADED from /home/mastag/.config/Lens/lens-weblink-store.json +1ms
info: ▪ 🔌 Starting LensProxy +5ms
info: ▪ [LENS-PROXY]: Proxy server has started at 127.0.0.1:44581 +2ms
info: ▪ 🔎 Testing LensProxy connection ... +1ms
info: ▪ ⚡ LensProxy connection OK +60ms
info: ▪ 🖥️ Starting WindowManager +1ms
APPIMAGE env is not defined, current application is not an AppImage
info: ▪ 🧩 Initializing extensions +14ms
info: ▪ [EXTENSION-DISCOVERY] loading extensions from /home/mastag/.config/Lens +0ms
info: ▪ [EXTENSION-INSTALLER] installing dependencies at /home/mastag/.config/Lens +25ms
info: ▪ [EXTENSION-INSTALLER] dependencies installed at /home/mastag/.config/Lens +364ms
info: ▪ [EXTENSION-DISCOVERY] watching extension add/remove in /home/mastag/.k8slens/extensions +1ms
Native extraction module not loaded, msgpackr will still run, but with decreased performance. Cannot find module 'msgpackr-extract'
Lens Cloud Extension activated
info: ▪ [C]: LOADED from /home/mastag/.config/Lens/extension-store/lenscloud-lens-extension/auth-token-store.json +34ms
info: ▪ [C]: LOADED from /home/mastag/.config/Lens/extension-store/lens-survey/preferences-store.json +1ms
telemetry main extension activated
info: ▪ [N]: LOADED from /home/mastag/.config/Lens/extension-store/lens-telemetry/preferences-store.json +24ms
info: ┏ [IPC-RENDERER]: adding extension listener +45ms
info: ┃ [1] {
info: ┃ [2] channel: 'deleteOneCluster',
info: ┃ [3] extension: { name: 'lenscloud-lens-extension', version: '5.2.6-latest.20211104.1' }
info: ┗ [4] }
info: ┏ [IPC-RENDERER]: adding extension listener +1ms
info: ┃ [1] {
info: ┃ [2] channel: 'loadRemoteSpacesClusters',
info: ┃ [3] extension: { name: 'lenscloud-lens-extension', version: '5.2.6-latest.20211104.1' }
info: ┗ [4] }
info: ┏ [IPC-RENDERER]: adding extension listener +0ms
info: ┃ [1] {
info: ┃ [2] channel: 'createOneSpace',
info: ┃ [3] extension: { name: 'lenscloud-lens-extension', version: '5.2.6-latest.20211104.1' }
info: ┗ [4] }
info: ┏ [IPC-RENDERER]: adding extension listener +3ms
info: ┃ [1] {
info: ┃ [2] channel: 'leaveOneSpace',
info: ┃ [3] extension: { name: 'lenscloud-lens-extension', version: '5.2.6-latest.20211104.1' }
info: ┗ [4] }
info: ▪ [EXTENSION]: enabled [email protected] +10ms
info: ▪ [EXTENSION]: enabled [email protected] +3ms
info: ▪ [EXTENSION]: enabled [email protected] +0ms
[CLUSTER-CONNECT] cluster proxy started on port 38309
[CLUSTER-CONNECT] cluster proxy is using aes-256-gcm for end-to-end encryption
info: ▪ [EXTENSION]: enabled [email protected] +9ms
[90289:1108/105103.368144:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Failed to generate minidump.Ongeldige instructie (geheugendump gemaakt)
Kubeconfig: Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
not applicable to this error
Additional context Using Gnome on X11 with NVidia graphics driver version 495.44
If you clone this repo locally and run make build and then run the .rpm within dist/ does it work for you then?
This seems to fail for me:
$ make build
yarn install --frozen-lockfile --network-timeout=100000
yarn install v1.22.10
[1/5] Validating package.json...
error [email protected]: The engine "node" is incompatible with this module. Expected version ">=14 <15". Got "16.11.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
make: *** [Makefile:20: node_modules] Fout 1
That is because you have [email protected] and we are still using [email protected].
You can use nvm to install the earlier version of node for just that shell.
Yes but F35 comes with node 16... I really don't want to pollute my system with older packages just to satisfy building Lens from source. Isn't there some other way around it?
No because each version of Electron work with a single version of node. In fact an electron binary bundles that version of node and chrome into it (or at least it should).
And we are currently using electron 13 which requires node 14.
Alright I used nvm to install version 14.18.1, then the make build completed. I now have OpenLens-5.3.0-alpha.9.1636387564264.x86_64.rpm which seems to work.
Okay thanks, the problem then might be that we are building the .rpm on Ubuntu and not a red-hat version of linux.
Perhaps so, I don't have a ubuntu based system to compare with. But thanks :)
I am going to leave this open so to track building the .rpm files on fedora instead of ubuntu
Current workaround is to start lens with
--disable-gpu-sandbox
Found in similar issue from vscode: https://github.com/microsoft/vscode/issues/134255#issuecomment-932387897
@Nokel81 Any plan to rebuild latest version RPM from a RedHat based distrib already? I'm using fedora and it seems that I also have to build from source.
Not in the next few weeks, but thanks for bringing this back up. I think we can do this sooner.
@Porasi We have very near plans to start building Lens Desktop on centOS and to also provide a YUM repo for faster and more convenient upgrades.