José Ribeiro

I installed this theme today and had the exact same need. I would suggest the same for the "About" button as well, once again for security reasons. From what I...

**+1**

@michaelCTS Thank you so so much for your work on this PR (and the reviewers for their feedback on it)! My humble suggestion/request for whoever picks up this wonderful work...

This is a duplicate of #10851, afaict. (Do you confirm, @andelf?)

To add my datapoint (which might or might not be related to this issue, as explained below), cutting (right click + cut) blocks almost always results in an unresponsive blank...

> After investigating, I see that better-sql3 expects to compile against Node 18. So, I applied an [overlay](https://github.com/T0modachi/.dotfiles/blob/main/system/configuration.nix#L154) to use electron_27 (Node 18), and there I confirmed that the problem...

Apologies for the wall of text, but I feel we need to re-center the discussion and make sure there's no confusion for those coming to this issue (and to link...

@schmittlauch as a quick workaround until this is fixed, ~launching Logseq using `logseq --disable-gpu` works for me~. **edit**: It becomes pretty unresponsive when GPU acceleration is disabled. (Also on NixOS,...

@sprocketc I feel silly. Yesterday I couldn't find Logseq's directory under `~/.config` (instructions above refer to Element), so I played with "related" ones... (`~/.config/Electron` didn't have `GPUCache`, messed with `chromium`'s...

While #10549 reports a different situation, many of the comments there specifically report this crash-during-block-copying. See [my comment](https://github.com/logseq/logseq/issues/10549#issuecomment-2073702192) on that issue for a summary of all reports. As on that...