Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot Run dbeaver after update to 3.5.6

See original GitHub issue

On Fedora 23, after updating from 3.5.5 to 3.5.6 using sudo rpm -U dbeaver-ce-3.5.6-stable.x86_64.rpm, I cannot run dbeaver anymore.

On statup, it gives an alert: “An error has occurred. See the log file /home/user/.eclipse/org.jkiss.dbeaver.product_3.5.6_620785679_linux_gtk_x86_64/configuration/1450103367507.log.”, then exits.

The log file contains:

!SESSION 2015-12-14 15:29:27.275 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_60
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86_64

!ENTRY org.eclipse.osgi 4 0 2015-12-14 15:29:28.427
!MESSAGE Application error
!STACK 1
java.lang.NullPointerException: null values not allowed
        at org.eclipse.core.internal.registry.ReferenceMap.put(ReferenceMap.java:351)
        at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.getBundle(RegistryStrategyOSGI.java:151)
        at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:166)
        at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
        at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
        at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1488)

Issue Analytics

State:
Created 8 years ago
Comments:13 (6 by maintainers)

Top GitHub Comments

2reactions

serge-ridercommented, Dec 14, 2015

Try to run it as

dbeaver -clean

Usually that fixes version update issues.

0reactions

serge-ridercommented, Mar 25, 2018

@Bragyy it is a known issue. You also could install EA version (https://dbeaver.com/files/ea/) - it contains fix of that problem. We going to publish new EE version release soon.