[Bug 1786158] New: [abrt] eclipse-pydev: fatal_error(): python3.7 killed by SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1786158
Bug ID: 1786158
Summary: [abrt] eclipse-pydev: fatal_error(): python3.7 killed
by SIGABRT
Product: Fedora
Version: 31
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:62142914cd44d95d14af3f67d44ec467ebc198e8;
Component: eclipse-pydev
Assignee: mat.booth(a)redhat.com
Reporter: igiwatson(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jjohnstn(a)redhat.com, mat.booth(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Just got eclipse to install on fedora 31 (Bug 1759176).
Ran "eclipse -clean". Start window about workspace was too small to see items
within and would not resize.
Quit and repeated. Bug reporting fired up.
Version-Release number of selected component:
1:eclipse-pydev-7.4.0-2.module_f31+7109+c8a2863a
Additional info:
reporter: libreport-2.11.3
backtrace_rating: 4
cgroup: 0::/user.slice/user-1004.slice/session-2.scope
cmdline: /usr/bin/python -u
/usr/lib/eclipse/droplets/pydev/plugins/org.python.pydev.core_7.4.0.v20191120-1833/pysrc/pycompletionserver.py
37889
crash_function: fatal_error
executable: /usr/bin/python3.7
journald_cursor:
s=3f6a6e26ec9e4d588ba7201c7140bbda;i=15015;b=03de9465244346889eabeaa10380d00a;m=c671631e;t=59a61c7f7ef85;x=17f3979af2d4b5d
kernel: 5.4.5-300.fc31.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1004
Truncated backtrace:
Thread no. 1 (6 frames)
#2 fatal_error at
/usr/src/debug/python3-3.7.5-2.fc31.x86_64/Python/pylifecycle.c:2187
#3 _Py_FatalInitError at
/usr/src/debug/python3-3.7.5-2.fc31.x86_64/Python/pylifecycle.c:2206
#4 pymain_init at
/usr/src/debug/python3-3.7.5-2.fc31.x86_64/Modules/main.c:3010
#5 pymain_main at
/usr/src/debug/python3-3.7.5-2.fc31.x86_64/Modules/main.c:3023
#6 _Py_UnixMain at
/usr/src/debug/python3-3.7.5-2.fc31.x86_64/Modules/main.c:3063
#8 _start
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1769351] New: groupinstall eclipse has broken dependencies
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1769351
Bug ID: 1769351
Summary: groupinstall eclipse has broken dependencies
Product: Fedora
Version: 31
Status: NEW
Component: eclipse
Assignee: mat.booth(a)redhat.com
Reporter: derrien(a)irisa.fr
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:
[root (Fedora 31) j]$ dnf groupinstall eclipse
Last metadata expiration check: 2:09:25 ago on Wed 06 Nov 2019 11:32:52 AM CET.
Error:
Problem 1: package eclipse-linuxtools-docker-7.2.0-4.fc31.noarch requires
osgi(org.glassfish.jersey.core.jersey-client), but none of the providers can be
installed
- package eclipse-linuxtools-docker-7.2.0-4.fc31.noarch requires
osgi(org.glassfish.jersey.core.jersey-common), but none of the providers can be
installed
- package eclipse-linuxtools-docker-7.2.0-4.fc31.noarch requires
osgi(org.glassfish.jersey.media.jersey-media-json-jackson), but none of the
providers can be installed
- package eclipse-linuxtools-docker-7.2.0-4.fc31.noarch requires jersey >=
2.28-3, but none of the providers can be installed
- conflicting requests
- package jersey-2.28-4.module_f31+6165+9b01e00c.noarch is excluded
- package jersey-2.28-4.module_f31+6519+12cd0b27.noarch is excluded
- nothing provides mvn(org.hibernate:hibernate-validator) needed by
jersey-2.28-5.fc31.noarch
- nothing provides mvn(org.jboss.weld.se:weld-se-core) needed by
jersey-2.28-5.fc31.noarch
Problem 2: package eclipse-cdt-docker-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.linuxtools.docker.core), but none of the providers can be
installed
- package eclipse-cdt-docker-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.linuxtools.docker.ui), but none of the providers can be
installed
- package eclipse-cdt-docker-2:9.7.0-1.fc31.x86_64 requires
eclipse-linuxtools-docker >= 5.3.0, but none of the providers can be installed
- package eclipse-linuxtools-docker-7.2.0-4.fc31.noarch requires
osgi(org.glassfish.jersey.core.jersey-client), but none of the providers can be
installed
- package eclipse-linuxtools-docker-7.2.0-4.fc31.noarch requires
osgi(org.glassfish.jersey.core.jersey-common), but none of the providers can be
installed
- package eclipse-linuxtools-docker-7.2.0-4.fc31.noarch requires
osgi(org.glassfish.jersey.media.jersey-media-json-jackson), but none of the
providers can be installed
- package eclipse-linuxtools-docker-7.2.0-4.fc31.noarch requires jersey >=
2.28-3, but none of the providers can be installed
- conflicting requests
- package eclipse-linuxtools-docker-7.4.0-2.module_f31+6519+12cd0b27.noarch
is excluded
- package jersey-2.28-4.module_f31+6165+9b01e00c.noarch is excluded
- package jersey-2.28-4.module_f31+6519+12cd0b27.noarch is excluded
- nothing provides mvn(org.hibernate:hibernate-validator) needed by
jersey-2.28-5.fc31.noarch
- nothing provides mvn(org.jboss.weld.se:weld-se-core) needed by
jersey-2.28-5.fc31.noarch
Problem 3: package eclipse-egit-github-5.3.0-1.fc31.noarch requires
eclipse-jgit >= 5.3.0, but none of the providers can be installed
- conflicting requests
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 4: package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >=
5.3.0, but none of the providers can be installed
- conflicting requests
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 5: package eclipse-mylyn-versions-git-3.25.0-0.6.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-mylyn-versions-git-3.25.0-0.6.fc31.noarch requires
osgi(org.eclipse.egit.core), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 6: package eclipse-linuxtools-vagrant-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.tm.terminal.view.core), but none of the providers can be
installed
- package eclipse-linuxtools-vagrant-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.tm.terminal.view.ui), but none of the providers can be
installed
- package eclipse-linuxtools-vagrant-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.tm.terminal.connector.ssh), but none of the providers can be
installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 7: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 8: package eclipse-egit-mylyn-5.3.0-2.fc31.noarch requires
osgi(org.eclipse.egit.core) = 5.3.0.201903130848.r, but none of the providers
can be installed
- package eclipse-egit-mylyn-5.3.0-2.fc31.noarch requires
osgi(org.eclipse.egit.ui) = 5.3.0.201903130848.r, but none of the providers can
be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 9: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-linuxtools-gprof-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.debug.core), but none of the providers can be installed
- package eclipse-linuxtools-gprof-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.launch), but none of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 10: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-linuxtools-gcov-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.ui), but none of the providers can be installed
- package eclipse-linuxtools-gcov-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.debug.core), but none of the providers can be installed
- package eclipse-linuxtools-gcov-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.launch), but none of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 11: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-linuxtools-systemtap-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.ui), but none of the providers can be installed
- package eclipse-linuxtools-systemtap-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.debug.core), but none of the providers can be installed
- package eclipse-linuxtools-systemtap-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.launch), but none of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 12: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-linuxtools-libhover-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.ui), but none of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 13: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-linuxtools-valgrind-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.ui), but none of the providers can be installed
- package eclipse-linuxtools-valgrind-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.debug.core), but none of the providers can be installed
- package eclipse-linuxtools-valgrind-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.launch), but none of the providers can be installed
- package eclipse-linuxtools-valgrind-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.codan.ui.cxx), but none of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 14: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-linuxtools-changelog-2:7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.ui), but none of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 15: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-linuxtools-perf-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.debug.core), but none of the providers can be installed
- package eclipse-linuxtools-perf-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.launch), but none of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 16: package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-mylyn-context-cdt-3.25.0-0.6.fc31.noarch requires
eclipse-cdt, but none of the providers can be installed
- package eclipse-mylyn-context-cdt-3.25.0-0.6.fc31.noarch requires
osgi(org.eclipse.cdt.ui), but none of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 17: package eclipse-linuxtools-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.ui), but none of the providers can be installed
- package eclipse-linuxtools-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.debug.core), but none of the providers can be installed
- package eclipse-linuxtools-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.launch), but none of the providers can be installed
- package eclipse-linuxtools-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.autotools.core), but none of the providers can be
installed
- package eclipse-linuxtools-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.cdt.managedbuilder.core), but none of the providers can be
installed
- package eclipse-cdt-2:9.7.0-1.fc31.x86_64 requires
osgi(org.eclipse.tm.terminal.control), but none of the providers can be
installed
- package eclipse-linuxtools-rpm-editor-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.linuxtools.profiling.launch) = 3.3.0.201903161739, but none of
the providers can be installed
- package eclipse-linuxtools-rpm-editor-7.2.0-4.fc31.noarch requires
osgi(org.eclipse.linuxtools.tools.launch.core) = 3.3.0.201903161739, but none
of the providers can be installed
- package eclipse-tm-terminal-4.5.100-1.fc31.noarch requires
osgi(org.eclipse.egit.ui), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- conflicting requests
- package eclipse-cdt-2:9.9.0-1.module_f31+6519+12cd0b27.x86_64 is excluded
- package eclipse-egit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded
- package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded
- package eclipse-tm-terminal-4.5.102-1.module_f31+6519+12cd0b27.noarch is
excluded
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
(try to add '--skip-broken' to skip uninstallable packages)
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1768671] New: eclipse-tests and eclipse-contributor-tools uninstallable
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1768671
Bug ID: 1768671
Summary: eclipse-tests and eclipse-contributor-tools
uninstallable
Product: Fedora
Version: 31
Status: NEW
Component: eclipse
Assignee: mat.booth(a)redhat.com
Reporter: phil(a)fifi.org
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:
eclipse-tests and eclipse-contributor-tools cannot be installed in Fedora 31.
Version-Release number of selected component (if applicable):
eclipse-contributor-tools-1:4.11-3.fc31.x86_64
eclipse-tests-1:4.11-3.fc31.x86_64
How reproducible:
Always
Steps to Reproduce:
1.dnf install eclipse-contributor-tools eclipse-tests
Actual results:
Error:
Problem 1: conflicting requests
- package eclipse-tests-1:4.11-3.fc31.x86_64 requires
osgi(org.eclipse.egit.core), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Problem 2: conflicting requests
- package eclipse-contributor-tools-1:4.11-3.fc31.x86_64 requires
osgi(org.eclipse.egit.core), but none of the providers can be installed
- package eclipse-egit-5.3.0-2.fc31.noarch requires eclipse-jgit >= 5.3.0,
but none of the providers can be installed
- nothing provides jgit = 5.3.0-5.fc31 needed by
eclipse-jgit-5.3.0-5.fc31.noarch
Expected results:
The packages should be installed.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1767770] New: Eclipse fails to start after update to Fedora 31
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1767770
Bug ID: 1767770
Summary: Eclipse fails to start after update to Fedora 31
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: eclipse
Severity: high
Assignee: mat.booth(a)redhat.com
Reporter: tom.tdw(a)gmail.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 1631438
--> https://bugzilla.redhat.com/attachment.cgi?id=1631438&action=edit
Eclipse log file including crash details.
Description of problem:
After upgrading to Fedora 31, opening eclipse fails and an error message is
shown, pointing to workspace/.metadata/.log , the contents of which are shown
(perhaps also including a successful launch after the crash?). The entries of
interest are those up until !ENTRY org.eclipse.osgi 4 0 2019-11-01
11:23:43.694, which includes the following error:
!ENTRY org.eclipse.osgi 4 0 2019-11-01 11:23:43.694
!MESSAGE Application error
!STACK 1
java.lang.NullPointerException
at
org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:181)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:385)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:260)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:589)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
at org.eclipse.equinox.launcher.Main.run(Main.java:1476)
at org.eclipse.equinox.launcher.Main.main(Main.java:1449)
Quite a few of the of the previous log entries refer to requirements not being
found.
It was possible to workaround this issue by deleting ~/.eclipse, however, this
is obviously not ideal behaviour on upgrade.
For interest, it seems that a similar bug was noted in 2010:
https://bugzilla.redhat.com/show_bug.cgi?id=601352
(I have not marked this as a duplicate since given how much time has passed
this is probably a distinct issue).
Version-Release number of selected component (if applicable):
How reproducible:
Steps to reproduce:
1. Use eclipse in Fedora 30
2. Upgrade to Fedora 31
3. Try to launch Eclipse
Actual results:
Crash
Expected results:
Eclipse opens successfully
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1670518] New: Cannot start eclipse-platform-4.10.0-2.fc30.x86_64
by bugzilla＠redhat.com
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.
3 years, 5 months
[Bug 1832892] New: eclipse corrupts JVM memory
by bugzilla＠redhat.com
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.
3 years, 5 months
[Bug 1759176] New: Eclipse fails to install out-of-the-box on F31
by bugzilla＠redhat.com
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.
3 years, 5 months
[Bug 1769032] New: Git integration no longer works after F31 upgrade
by bugzilla＠redhat.com
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.
3 years, 5 months