Logseq: Refusing to evaluate with Electron version 39.8.10 is EOL

[Crazzygamerr]

Nixpkgs version

• Stable (26.05)

Describe the bug

error: Refusing to evaluate package 'electron-39.8.10' in /nix/store/snzg7swkp0vsd2qch9izsbmxnyb13ca0-source/pkgs/development/tools/electron/binary/generic.nix:50 because it is marked as insecure

   Known issues:
    - Electron version 39.8.10 is EOL

Getting this error because Logseq has an input of electron_39 and that was marked insecure in #521310

I'm also seeing this issue for bitwarden-desktop, and am currently overriding the input to electron_40 in my config.
I would be happy to contribute the fix! Might need a little direction as I haven't worked with nixpkgs before.

Steps to reproduce

Add logseq to home.packages and configuration build should fail.
Not sure how one would reproduce this from a nixpkgs repo.

Expected behaviour

Build successfully without errors

Screenshots

No response

Relevant log output

Additional context

No response

System metadata

• system: "x86_64-linux"
• host os: Linux 6.12.80, NixOS, 25.11 (Xantusia), 25.11.20260410.54170c5
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.31.4
• nixpkgs: /nix/store/m5dr0w2wb9lca77ar3idab31szd6mix7-source

Notify maintainers

@TomaSajt

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.
• I assert that I have read the automation/AI policy and that this issue report complies with it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.

[luringens]

Apparently logseq plugins break if you try to force the current version to run on a newer Electron. But there is a recent nightly release that support it, which this PR is working on: #516682

[TomaSajt]

That PR packages the new, db based Logseq.
I don't know how compatible it is with the current logseq, and it is still in development.
I am still working on a way to patch the current version to work with electron 40+

Until then, you can either ignore the insecure warning and build logseq yourself.
Or you can also just have a separate pinned nixpkgs pointing at a revision where Electron 39 was not marked insecure, because then you can use the cache and not have to build it yourself.

[TomaSajt]

Just in case people don't stumble into the other issue, I shared in a comment a not-too-convoluted way of using logseq from an old nixpkgs revision.
#535206 (comment)

I still don't have any good news from upstream.
If you want to, you can leave some support on this issue: logseq/og#32

[quickdudley]

I have changed the logseq in my home.packages to (logseq.override { electron_39 = electron; }) and haven't noticed any problems with it, though I wasn't using any plugins.

[TomaSajt]

If you're not using plugins, yeah, it works fine with newer electron versions AFAICT.