https://bugzilla.redhat.com/show_bug.cgi?id=1670518
Bug ID: 1670518
Summary: Cannot start eclipse-platform-4.10.0-2.fc30.x86_64
Product: Fedora
Version: rawhide
Status: NEW
Component: eclipse
Assignee: mat.booth(a)redhat.com
Reporter: lslebodn(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
dbhole(a)redhat.com, ebaron(a)fedoraproject.org,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, jjohnstn(a)redhat.com,
lef(a)fedoraproject.org, mat.booth(a)redhat.com,
rgrunber(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1524767
--> https://bugzilla.redhat.com/attachment.cgi?id=1524767&action=edit
.metadata/.log
Description of problem:
I tried to start eclipse with empty workspace and it failed
Version-Release number of selected component (if applicable):
sh$ rpm -qa eclipse\* | sort
eclipse-cdt-9.6.0-4.fc30.x86_64
eclipse-cdt-native-9.6.0-4.fc30.x86_64
eclipse-ecf-core-3.14.4-1.fc30.noarch
eclipse-egit-5.2.0-1.fc30.noarch
eclipse-emf-core-2.16.0-1.fc30.noarch
eclipse-equinox-osgi-4.10.0-2.fc30.x86_64
eclipse-jdt-4.10.0-2.fc30.noarch
eclipse-jgit-5.2.0-2.fc30.noarch
eclipse-launchbar-2.2.2-1.fc30.noarch
eclipse-linuxtools-libhover-7.1.0-1.fc30.noarch
eclipse-platform-4.10.0-2.fc30.x86_64
eclipse-remote-3.0.0-0.6.git14c6611.fc30.noarch
eclipse-rse-3.7.100-1.fc30.noarch
eclipse-swt-4.10.0-2.fc30.x86_64
eclipse-tm-terminal-4.4.0-4.fc30.noarch
eclipse-tm-terminal-connectors-4.4.0-4.fc30.noarch
How reproducible:
Deterministic on my machine (did not try on another laptop)
Steps to Reproduce:
1. create empty directory in homedir
2. /usr/bin/eclipse
3. choose directory created in the 1st step as workspace
Actual results:
failed to open IDE
Expected results:
IDE started without any problem
Additional info:
there are some exceptions in .metadata/.log
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1879576
Bug ID: 1879576
Summary: eclipse-4.17 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: eclipse
Keywords: FutureFeature, Triaged
Assignee: mat.booth(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
dbhole(a)redhat.com, ebaron(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, jjohnstn(a)redhat.com,
lef(a)fedoraproject.org, mat.booth(a)redhat.com,
rgrunber(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 4.17
Current version/release in rawhide: 4.16-13.fc34
URL: https://download.eclipse.org/eclipse/downloads/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/653/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1832892
Bug ID: 1832892
Summary: eclipse corrupts JVM memory
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: eclipse
Severity: high
Assignee: mat.booth(a)redhat.com
Reporter: rwestrel(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
dbhole(a)redhat.com, ebaron(a)fedoraproject.org,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, jjohnstn(a)redhat.com,
lef(a)fedoraproject.org, mat.booth(a)redhat.com,
rgrunber(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Running a fastdebug JDK with eclipse causes a crash:
$ eclipse -vm
~/jdk-updates-jdk11u-dev/build/linux-x86_64-normal-server-fastdebug/images/jdk/bin
CompileCommand: exclude
org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith
CompileCommand: exclude
org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.<init>
CompileCommand: exclude
org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate
CompileCommand: exclude
org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding
CompileCommand: exclude
org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile
CompileCommand: exclude
org/eclipse/tycho/core/osgitools/EquinoxResolver.newState
[5.759s][warning][malloc,free] ## nof_mallocs = 676800, nof_frees = 139068
[5.759s][warning][malloc,free] ## memory stomp:
[5.759s][warning][malloc,free] GuardedMemory(0x00007f67a3e04380)
base_addr=0x00007f679ce592c0 tag=0x0000000000000000 user_size=1
user_data=0x00007f679ce592e0
[5.759s][warning][malloc,free] Header guard @0x00007f679ce592c0 is OK
[5.759s][warning][malloc,free] Trailer guard @0x00007f679ce592e1 is BROKEN
[5.759s][warning][malloc,free] User data appears to be in use
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc: SuppressErrorAt=/os.cpp:638
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error
(/home/roland/jdk-updates-jdk11u-dev/src/hotspot/share/runtime/os.cpp:638),
pid=3260907, tid=3260908
# fatal error: memory stomping error
#
# JRE version: OpenJDK Runtime Environment (11.0.5) (fastdebug build
11.0.5-internal+0-adhoc.roland.jdk-updates-jdk11u-dev)
# Java VM: OpenJDK 64-Bit Server VM (fastdebug
11.0.5-internal+0-adhoc.roland.jdk-updates-jdk11u-dev, mixed mode, tiered,
compressed oops, g1 gc, linux-amd64)
# 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/roland/core.3260907)
#
# An error report file with more information is saved as:
# /home/roland/hs_err_pid3260907.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
Current thread is 3260908
Dumping core ...
The JVM reports that something overwrote its own memory.
Version-Release number of selected component (if applicable):
Fedora 31, eclipse 19.09
A colleague of mine reports a similar issue on Fedora 32
One of our users reports a similar issue on RHEL 7.4
How reproducible:
Always with a fastdebug build
Steps to Reproduce:
1. clone openjdk11:
hg clone https://hg.openjdk.java.net/jdk-updates/jdk11u-dev
2. configure and build:
bash ./configure --enable-debug --disable-warnings-as-errors
make images
3. run eclipse with the new build:
eclipse -vm
~/jdk-updates-jdk11u-dev/build/linux-x86_64-normal-server-fastdebug/images/jdk/bin
Actual results:
crashes
Expected results:
should not crash
Additional info:
I ran this under rr (https://rr-project.org/) to pinpoint the root cause of the
corruption:
$ rr record eclipse -vm
~/jdk-updates-jdk11u-dev/build/linux-x86_64-normal-server-fastdebug/images/jdk/bin
eclipse reports same error message as above. It includes a pid:
# Internal Error
(/home/roland/jdk-updates-jdk11u-dev/src/hotspot/share/runtime/os.cpp:638),
pid=3263056, tid=3263057
Now replaying the execution of that process:
$ rr replay -p 3263056
(rr) handle SIGSEGV nostop noprint pass
(rr) cont
error message printed again here. Now let's set a watchpoint at the memory
location that's corrupted and execute backward:
(rr) watch -l *(char*)0x00007fd448fa0901
(rr) reverse-cont
(rr) reverse-cont
Thread 2 hit Hardware watchpoint 1: -location *(char*)0x00007fd448fa0901
Old value = 0 '\000'
New value = -85 '\253'
0x00007fd4166ccfaf in value_lcopy_boolean () from /lib64/libgobject-2.0.so.0
(rr) where
#0 0x00007fd4166ccfaf in value_lcopy_boolean () from
/lib64/libgobject-2.0.so.0
#1 0x00007fd4166ab42f in g_object_get_valist () from
/lib64/libgobject-2.0.so.0
#2 0x00007fd4166ab844 in g_object_get () from /lib64/libgobject-2.0.so.0
#3 0x00007fd3f4412311 in
Java_org_eclipse_swt_internal_gtk_OS__1g_1object_1get__J_3B_3ZJ () from
/usr/lib/eclipse/plugins/org.eclipse.swt.gtk.linux.x86_64_3.112.0.v20190908-0312/libswt-pi3-gtk-4928r15.so
#4 0x00007fd43095758b in ?? ()
#5 0x00007fd3f45667e0 in ?? ()
#6 0x00000000000000d8 in ?? ()
#7 0x00000000000000d8 in ?? ()
#8 0x00007fd448020000 in ?? ()
#9 0x00007fd3f4624400 in ?? ()
#10 0x00007fd430956b1d in ?? ()
#11 0x00007fd44ec65600 in ?? ()
#12 0x00007fd3f45667e0 in ?? ()
#13 0x00007fd44ec65690 in ?? ()
#14 0x00007fd3f4580040 in ?? ()
#15 0x0000000000000000 in ?? ()
That eclipse method above causes the memory corruption AFAIU.
Note that this triggers with a fastdebug build of the JDK but most likely
causes silent memory corruption with a release build.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1759176
Bug ID: 1759176
Summary: Eclipse fails to install out-of-the-box on F31
Product: Fedora
Version: 31
Status: NEW
Component: eclipse
Severity: high
Assignee: mat.booth(a)redhat.com
Reporter: mat.booth(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
dbhole(a)redhat.com, ebaron(a)fedoraproject.org,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, jjohnstn(a)redhat.com,
lef(a)fedoraproject.org, mat.booth(a)redhat.com,
rgrunber(a)redhat.com
Target Milestone: ---
Classification: Fedora
When you attempt to install Eclipse on F31 you get the following error:
[mbooth@fedora31 ~]$ sudo dnf install eclipse
Last metadata expiration check: 0:24:07 ago on Mon 07 Oct 2019 14:28:53 BST.
Error:
Problem: package eclipse-jdt-1:4.11-3.fc31.noarch requires eclipse-platform =
1:4.11-3.fc31, but none of the providers can be installed
- package eclipse-platform-1:4.11-3.fc31.x86_64 requires glassfish-el >=
3.0.1, but none of the providers can be installed
- conflicting requests
- package glassfish-el-3.0.1-0.12.b08.module_f31+6519+12cd0b27.noarch is
excluded
- package glassfish-el-3.0.1-0.11.b08.fc31.noarch is excluded
(try to add '--skip-broken' to skip uninstallable packages)
There are two "workarounds":
1) Users must first enable the eclipse module to install the latest version of
modular Eclipse:
[mbooth@fedora31 ~]$ sudo dnf module enable eclipse:latest
2) Users must first disable all conflicting java modules to install obsolete
ursine version of Eclipse:
[mbooth@fedora31 ~]$ sudo dnf module disable eclipse maven
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1769032
Bug ID: 1769032
Summary: Git integration no longer works after F31 upgrade
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: eclipse-jgit
Severity: medium
Assignee: mat.booth(a)redhat.com
Reporter: Gary.Duzan(a)fisglobal.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, mat.booth(a)redhat.com,
rgrunber(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
With Eclipse CDT, git projects no longer have git functions after Fedora 30->31
upgrade.
Version-Release number of selected component (if applicable):
jgit-5.4.0-6.module_f31+6165+9b01e00c.noarch
eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch
How reproducible:
Reliably fails on git startup
Steps to Reproduce:
1. Configure eclipse-cdt with a workspace containing git projects
2. Upgrade Fedora from 30 to 31
3. Start eclipse
Actual results:
Various missing icons, missing git functionality, and "Could not create the
view: org.eclipse.egit.ui.RepositoriesView" in the "Git Repositories" tab.
Expected results:
Normal git functions
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1893343
Bug ID: 1893343
Summary: F34FailsToInstall: eclipse-jgit
Product: Fedora
Version: rawhide
Status: NEW
Component: eclipse-jgit
Assignee: mat.booth(a)redhat.com
Reporter: mhroncok(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, mat.booth(a)redhat.com,
rgrunber(a)redhat.com
Blocks: 1868279 (F34FailsToInstall)
Target Milestone: ---
Classification: Fedora
Hello,
Please note that this comment was generated automatically. If you feel that
this output has mistakes, please contact me via email (mhroncok(a)redhat.com)
Your package (eclipse-jgit) Fails To Install in Fedora 34:
can't install eclipse-jgit:
- nothing provides jgit = 5.8.1 needed by eclipse-jgit-5.8.1-1.fc34.noarch
If you know about this problem and are planning on fixing it, please
acknowledge so by setting the bug status to ASSIGNED. If you don't have time to
maintain this package, consider orphaning it, so maintainers of dependent
packages realize the problem.
If you don't react accordingly to the policy for FTBFS/FTI bugs
(https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…)
your package may be orphaned in 8+ weeks.
P.S. The data was generated solely from koji buildroot, so it might be newer
than the latest compose or the content on mirrors.
P.P.S. If this bug has been reported in the middle of upgrading multiple
dependent packages, please consider using side tags:
https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/
Thanks!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1868279
[Bug 1868279] (F34FailsToInstall) - Fedora 34 Fails To install Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.