Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot Start Dbeaver After Update (24.0.3 -> 24.0.5) on Windows Server 2008 R2 Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library #34034

Open
tugalsan opened this issue May 22, 2024 · 3 comments

Comments

@tugalsan
Copy link

Description

I cannot Start dbeaver, after updating from 24.0.3 to 24.0.5 on Windows Server 2008 R2. The error in the log says Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library

DBeaver Version

Community Edition 24.0.3 -> 24.0.5

Operating System

Windows Server 2008 R2

Database and driver

database: mariadb-10.4.33-winx64
driver: org.mariadb.jdbc.Driver

Steps to reproduce

  1. On my pc (Windows Server 2008 R2) , I had a running dbeaver (24.0.3).
  2. It asked for update at startup, I did download the update and extract to a clean folder.
  3. When I run the updated dbeaver (24.0.5) it caused attached error.

Additional context

see the startup error log
1716420482960.log

@E1izabeth
Copy link
Member

Thank you for your report. We have reproduced the issue and are investigating.

@chrisv5
Copy link

chrisv5 commented Jun 6, 2024

Also happens on Windows Server 2012 R2 and DBeaver 24.1.0. My error log is identical (minus the paths, obviously) with those of the OP. I had to revert to 24.0.4.

@arhayka
Copy link
Member

arhayka commented Jun 17, 2024

Unfortunately, after upgrading to Eclipse 2024-06, the following OS are no longer supported: Windows 8, macOS 10, and Windows Server 2012. This issue is not on DBeaver side, you can see the details here: eclipse-platform/eclipse.platform.swt#1252.

We have already added the system requirements to the download pages and are working on ways to warn users before the update.

However, we will keep an eye on the situation and try to do something if possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants