Change:
cp -r * $out/opt/dbeaver makeWrapper $out/opt/dbeaver/dbeaver $out/bin/dbeaver  --prefix PATH : "${openjdk17}/bin"  <del> --set JAVA_HOME "${openjdk17.home}" </del> <ins> --set JAVA_HOME "${openjdk17.home}"  --prefix CLASSPATH : "$out/dbeaver/plugins/*:${swt}/jars/swt.jar"  --prefix LD_LIBRARY_PATH : "$out/lib:${ lib.makeLibraryPath [ swt gtk3 glib ] }" </ins> mkdir -p $out/share/icons/hicolor/256x256/apps ln -s $out/opt/dbeaver/dbeaver.png $out/share/icons/hicolor/256x256/apps/dbeaver.png

Discussion:
dbeaver does not start Steps to reproduce the behavior: dbeaver it's gui appears <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I can't reproduce this. I'm guessing something is wrong with how we pass the java installation to dbeaver. Seems like fixed a similar issue. Can you try going into a nix shell with package and launch dbeaver?
Am I did it right?
and when I ran from nixpkgs-unstable it worked
You did it right, it was just a wild guess from me and it didn't work. That's good news that it worked for you before, can you git bisect it?
I found the last commit I can use, and it is the one before staging was merged ( May be can help us?
there was some changes in openjdk17, like this: but I can't find anything about SWT
I don't recall anything relevant in that merge, but it touched almost a thousand files.
I've been hit by this today. I've noticed that dbeaver (or SWT underneath) says that it can't find swt-pi3 and it's trying to use swt-pi4 as fallback, but in my home dir there is this file: I've tried to remove but it got recreated after running dbeaver again. Maybe this can help find the problem...
Maybe that file is a product of the error, I don't have it:
I see that dbeaver depends on jdk17. Shouldn't it depend on 21 instead?
Same problem with , not sure which commit introduced it but it was recent.
They recommend jdk17:
Same issue here. Has anyone found a temporary workaround?
I'm using this in flake: inputs.dbeaver- = "github:nixos/nixpkgs/"; and in environment.systemPackages: inputs.dbeaver-last.legacyPackages.x86_64- i.e. last commit with worked dbeaver-bin
Amazing. Thanks !
I've switched to the flatpak version (works on Linux...)
Could it be the reason? !

once I had an adventure after my own "remove unused arguments" =)
4 is working fine
Hm I just grabbed this commit and it's not launching for me still, I cleared out all directories too (, , ). Using it like this and
I'm using master branch, may be some other package which is the hidden runtime dependency was updated too?
I have again the same issue (
temporary workaround this works for me inputs.dbeaver- = "github:nixos/nixpkgs/"; while this commit not dbeaver- = "github:NixOS/nixpkgs/";
Had the same issue. After stracing dbeaver, it looks like it could not find the libgtk-3.so. After installing the libgtk-3-0 package on my debian, it starts like a charm.
For me: Works on NixOS 24.05 On Ubuntu 22.04 out of the box: nix run github:nixos/nixpkgs/24.05#dbeaver-bin : fails nix run github:nixos/nixpkgs/23.11#dbeaver-bin : fails nix run github:nixos/nixpkgs/23.05#dbeaver : fails nix run github:nixos/nixpkgs/22.11#dbeaver : works stracing the failure here's the problem: Repro on any Linux distro:
big thanks for the reproduction commands! For me works and fails using the reproduction environment you provided. This too confirms that the recent staging merge caused this issue. I'm surprised it didn't work for you on 24.05. <details<summarystrace on 24.05</summary</details
I cherry picked openjdk related commits onto the last known good commit before the staging merge () and I bisected it to a single commit that is causing the issue: . If you want to quickly verify this is the failing commit (trying to build that exact commit will take a long time), I made a branch which has the good commit as the base and the bad commit cherry picked. I don't have much time right now to look into what does the failing commit exactly do and how to fix this, anyone feel free to continue from here :)
Try .
I can confirm, it's fixed now for my system too Can we wait for 24.1.5 soon?

=)
This tracks when the fix will be released in which unstable channel:
I'm already have it - I use nixpkgs/master as a daily driver for a long time 5 was yesterday's release =)