Package Details: eclipse-cpp-bin 2:4.31-2

Git Clone URL: (read-only, click to copy)
Package Base: eclipse-cpp-bin
Description: Highly extensible IDE (C/C++ version)
Upstream URL:
Licenses: EPL
Conflicts: eclipse
Provides: eclipse
Submitter: qimuzi
Maintainer: altermetax
Last Packager: altermetax
Votes: 9
Popularity: 0.71
First Submitted: 2023-10-03 19:28 (UTC)
Last Updated: 2024-04-29 14:31 (UTC)

Dependencies (3)

Required by (26)

Sources (3)

Latest Comments

1 2 3 4 Next › Last »

Muflone commented on 2024-04-29 22:52 (UTC)

@altermetax the others packages could be merged in the case someone files valid requests and the -bin packages exist

altermetax commented on 2024-04-29 22:34 (UTC) (edited on 2024-04-29 22:35 (UTC) by altermetax)

@Muflone thanks, I adopted eclipse-cpp-bin. I assume the same should also be done with the other Eclipse packages I maintain (-java, jee, -php, -dsl)?

Muflone commented on 2024-04-27 15:54 (UTC) (edited on 2024-04-27 15:55 (UTC) by Muflone)

@altermetax please adopt the eclipse-cpp package as this package will be merged into eclipse-cpp-bin (and consequentially the package eclipse-cpp will be removed) as this package is not built from sources but uses a prebuilt binary

altermetax commented on 2024-04-15 11:36 (UTC)

Yeah, ~/.eclipse is where the plugins are installed. I have no idea what could have caused this, unfortunately. I believe it's an issue upstream, since this PKGBUILD doesn't do much apart from pulling down the upstream build, installing it in /usr/lib/eclipse and installing the icons and the desktop entry.

snack commented on 2024-04-15 11:32 (UTC)

Yes, when running with the WEBKIT_DISABLE_DMABUF_RENDERER=1 variable no error occurs for the marketplace. But no plugins are there, I guess because of the fresh ~/.eclipse. Restoring the previous ~/.eclipse the marketplace is gone again, so I guess something is badly screwed there. I'll restart with fresh ~/.eclipse and reinstall the plugins.

altermetax commented on 2024-04-15 10:40 (UTC)

This is when you run /usr/lib/eclipse/eclipse directly, right?

snack commented on 2024-04-15 10:38 (UTC)

With a fresh ~/.eclipse I got the martketplace back, but old plugins are gone. Furthermore the marketplace generates this crash:

(Eclipse:32624): Gdk-CRITICAL **: 12:37:52.505: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed
# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x000078b174ec690b, pid=32624, tid=32625
# JRE version: OpenJDK Runtime Environment Temurin-17.0.10+7 (17.0.10+7) (build 17.0.10+7)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.10+7 (17.0.10+7, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  []
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/mori/software/devel/core.32624)
# An error report file with more information is saved as:
# /home/mori/software/devel/hs_err_pid32624.log
# If you would like to submit a bug report, please visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

and gets stuck until I kill everything manually. This happens also with a fresh .metadata.

altermetax commented on 2024-04-15 10:21 (UTC)

@snack In theory, the original issue shouldn't affect plugins at all, it's a problem with the embedded Gtk WebKit. Maybe you could try with a fresh ~/.eclipse and see if the plugins are still broken? I tried multiple times, but I can't reproduce this.

snack commented on 2024-04-15 10:06 (UTC)

@altermetax That helps with -data, which now works again, but all the plugins are still not working. Maybe the original issue screwed the ~/.eclipse folder?

altermetax commented on 2024-04-15 10:01 (UTC)

@snack: I'm not experiencing these issues. The last package update set the environment variable WEBKIT_DISABLE_DMABUF_RENDERER=1 to work around an issue until the next Eclipse release (see To check if that's the culprit, could you try running /usr/lib/eclipse/eclipse directly and checking whether that solves the problem?