[Bug 1873489] New: Xorg/Wayland crash on os.kill(0, 15) executed from eclipse python debugger
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1873489
Bug ID: 1873489
Summary: Xorg/Wayland crash on os.kill(0, 15) executed from
eclipse python debugger
Product: Fedora
Version: 32
Status: NEW
Component: eclipse-pydev
Assignee: mat.booth(a)redhat.com
Reporter: ldoktor(a)redhat.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:
When debugging certain app I got Wayland crashes, then reproduced it on Xorg as
well. Simplest reproduction I got to is to create a file that executes
"os.kill(0, 15)" and run/debug it from eclipse.
Version-Release number of selected component (if applicable):
eclipse-equinox-osgi-4.14-5.fc32.x86_64
eclipse-jgit-5.6.0-2.fc32.noarch
eclipse-jdt-4.14-5.fc32.noarch
eclipse-pydev-7.7.0-1.fc32.x86_64
eclipse-egit-5.6.0-2.fc32.noarch
eclipse-swt-4.14-5.fc32.x86_64
eclipse-ecf-core-3.14.6-4.fc32.noarch
eclipse-platform-4.14-5.fc32.x86_64
eclipse-emf-core-2.20.0-5.fc32.noarch
libwayland-egl-1.18.0-1.fc32.i686
libwayland-server-1.18.0-1.fc32.x86_64
xorg-x11-server-Xwayland-1.20.8-1.fc32.x86_64
qt5-qtwayland-5.14.2-4.fc32.x86_64
gnome-session-wayland-session-3.36.0-2.fc32.x86_64
xorg-x11-server-Xorg-1.20.8-1.fc32.x86_64
How reproducible:
Always
Steps to Reproduce:
1. create a python file with "import os; os.kill(0, 15)"
2. select "Run As"->"Python Run"
Actual results:
Eclipse crashes and Wayland/Xorg as well (Xorg restarts, Wayland stays dead)
Expected results:
Ideally Eclipse should stay unaffected but at least it'd be nice if
Wayland/Xorg survived.
Additional info:
It also works when I start debugging any script and manually execute the
"os.kill(0, 15)" from the pydev console. On the other hand everything works
well when the process is started elsewhere and pydev is only accessed via
"import pydevd; pydevd.settrace("127.0.0.1", True, True)" directly from the
script (execution only kills the python process, Eclipse as well as
Wayland/Xorg survives)
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years
[Bug 1888339] New: Error unpacking rpm package eclipse-platform-1:4.16-13.fc33.x86_64
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1888339
Bug ID: 1888339
Summary: Error unpacking rpm package
eclipse-platform-1:4.16-13.fc33.x86_64
Product: Fedora
Version: 33
Status: NEW
Component: eclipse
Assignee: mat.booth(a)redhat.com
Reporter: mycroft8(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)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
One RPM file associated with Eclipse in Fedora 33 beta is not installable.
Error unpacking rpm package eclipse-platform-1:4.16-13.fc33.x86_64
And the verification step fails.
This is a continuation of the same issue since Fedora 32.
It does not help to completely remove and re-install Eclipse. The issue
remains. It does not help to specifically enable the "latest" Eclipse.
The only workaround I can find is to not use Fedora repo's for Eclipse.
To reproduce, just try sudo dnf install eclipse-platform
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 1 month
[Bug 1840743] New: Eclipse won't open after installing eclipse-mpc
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1840743
Bug ID: 1840743
Summary: Eclipse won't open after installing eclipse-mpc
Product: Fedora
Version: 32
Status: NEW
Component: eclipse-mpc
Assignee: mat.booth(a)redhat.com
Reporter: doug.hs(a)protonmail.ch
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1692717
--> https://bugzilla.redhat.com/attachment.cgi?id=1692717&action=edit
Error log
Description of problem:
After installing the package eclipse-mpc, Eclipse fails right after selecting
the workspace and clicking "Launch". See attached logs.
Version-Release number of selected component (if applicable):
1.8.1
How reproducible:
Always
Steps to Reproduce:
1. Install Eclipse from GNOME Software (from Fedora 32 repositories).
2. Install Eclipse PDT (from Eclipse repositories, using "Install New Software"
in the "Help" menu).
3. Install Eclipse Marketplace (dnf install eclipse-mpc).
4. Add/Select a workspace and try to launch it.
Actual results:
Instead of the Eclipse main window, I see a small popup saying an error has
occurred and that I should check the logs at
"~/eclipse-workspace/.metadata/.log". Eclipse then closes itself.
Expected results:
Eclipse should load the workspace as usual.
Additional info:
Creating a new workspace and launching it does not fix the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1889065] New: cannot upgrade eclipse-mylyn from f32 to f33
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1889065
Bug ID: 1889065
Summary: cannot upgrade eclipse-mylyn from f32 to f33
Product: Fedora
Version: 32
Status: NEW
Component: eclipse-mylyn
Assignee: extras-orphan(a)fedoraproject.org
Reporter: heldwin(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
extras-orphan(a)fedoraproject.org, jerboaa(a)gmail.com,
jjohnstn(a)redhat.com, rgrunber(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
While trying to upgrade one of my system from f323 to f33, I got these
messages.
Command used: dnf distro-sync --releasever=33
Version-Release number of selected component (if applicable):
eclipse-mylyn-3.25.0-3.fc32.noarch
eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch
glassfish-jaxb-api-2.2.12-14.fc32.noarch
Errors:
Problem 1: package eclipse-mylyn-3.25.0-3.fc32.noarch requires osgi(jaxb-api),
but none of the providers can be installed
- glassfish-jaxb-api-2.2.12-14.fc32.noarch does not belong to a distupgrade
repository
- problem with installed package eclipse-mylyn-3.25.0-3.fc32.noarch
Problem 2: package jaxb-api-2.3.3-2.fc33.noarch obsoletes glassfish-jaxb-api <
2.3.3-2 provided by glassfish-jaxb-api-2.2.12-14.fc32.noarch
- package jaxb-runtime-2.3.3-4.fc33.noarch requires
mvn(jakarta.xml.bind:jakarta.xml.bind-api), but none of the providers can be
installed
- package eclipse-mylyn-3.25.0-3.fc32.noarch requires osgi(jaxb-api), but
none of the providers can be installed
- problem with installed package glassfish-jaxb-core-2.2.11-16.fc32.noarch
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.commons.core) = 3.25.0.v20200816.1126, but none of the
providers can be installed
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.commons.net) = 3.25.0.v20200816.1126, but none of the
providers can be installed
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.commons.repositories.core) = 1.17.0.v20200816.1126, but
none of the providers can be installed
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.commons.repositories.http.core) = 1.17.0.v20200816.1126,
but none of the providers can be installed
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.commons.ui) = 3.25.0.v20200816.1126, but none of the
providers can be installed
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.commons.workbench) = 3.25.0.v20200816.1126, but none of
the providers can be installed
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.commons.xmlrpc) = 3.25.0.v20200816.1126, but none of the
providers can be installed
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.tasks.core) = 3.25.0.v20200816.1126, but none of the
providers can be installed
- package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires
osgi(org.eclipse.mylyn.tasks.ui) = 3.25.0.v20200816.1126, but none of the
providers can be installed
- glassfish-jaxb-core-2.2.11-16.fc32.noarch does not belong to a distupgrade
repository
- problem with installed package
eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch
Removing eclipse-mylyn pulls with it:
apache-commons-lang-2.6-27.fc32.noarch
bea-stax-api-1.2.0-20.fc32.noarch
eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch
glassfish-fastinfoset-1.2.15-2.fc32.noarch
glassfish-jaxb-api-2.2.12-14.fc32.noarch
glassfish-jaxb-core-2.2.11-16.fc32.noarch
glassfish-jaxb-runtime-2.2.11-16.fc32.noarch
glassfish-jaxb-txw2-2.2.11-16.fc32.noarch
google-gson-2.8.6-3.fc32.noarch
istack-commons-runtime-2.21-12.fc32.noarch
jakarta-commons-httpclient-1:3.1-33.fc32.noarch
relaxngDatatype-2011.1-12.fc32.noarch
1stax-ex-1.7.7-12.fc32.noarch
xmlstreambuffer-1.5.4-11.fc32.noarch
xsom-20140514-3.fc32.noarc
but then we cannot add again eclipse-mylyn as it is not in f33 repo, if I look
bug #1831437 (retired package)
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1862776] New: eclipse does not start after (atleast) upgrade to F31
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1862776
Bug ID: 1862776
Summary: eclipse does not start after (atleast) upgrade to F31
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: eclipse
Severity: high
Assignee: mat.booth(a)redhat.com
Reporter: customercare(a)resellerdesktop.de
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 1703200
--> https://bugzilla.redhat.com/attachment.cgi?id=1703200&action=edit
startup crash logfile
Description of problem:
Eclipse does show the splash screen on startup, but does crash with:
!ENTRY org.eclipse.osgi 4 0 2020-08-02 13:47:30.736
!MESSAGE Anwendungsfehler
!STACK 1
java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench" could
not be found in the registry. The applications available are:
org.eclipse.wst.server.preview.preview,
org.eclipse.wst.jsdt.core.JavaCodeFormatter, org.eclipse.ant.core.antRunner,
org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director,
org.eclipse.equinox.p2.garbagecollector.application,
org.eclipse.equinox.p2.publisher.InstallPublisher,
org.eclipse.equinox.p2.publisher.EclipseGenerator,
org.eclipse.equinox.p2.publisher.ProductPublisher,
org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher,
org.eclipse.equinox.p2.reconciler.application,
org.eclipse.equinox.p2.repository.repo2runnable,
org.eclipse.equinox.p2.repository.metadataverifier,
org.eclipse.equinox.p2.artifact.repository.mirrorApplication,
org.eclipse.equinox.p2.metadata.repository.mirrorApplication,
org.eclipse.equinox.p2.touchpoint.natives.nativePackageExtractor,
org.eclipse.equinox.p2.updatesite.UpdateSitePublisher,
org.eclipse.equinox.p2.publisher.UpdateSitePublisher,
org.eclipse.equinox.p2.publisher.CategoryPublisher,
org.eclipse.help.base.infocenterApplication,
org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool,
org.eclipse.xsd.ecore.importer.XSD2GenModel, org.eclipse.pde.build.Build,
org.eclipse.pde.junit.runtime.uitestapplication,
org.eclipse.pde.junit.runtime.legacytestapplication,
org.eclipse.pde.junit.runtime.coretestapplication,
org.eclipse.pde.junit.runtime.coretestapplicationnonmain,
org.eclipse.pde.junit.runtime.nonuithreadtestapplication,
org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaCodeFormatter,
org.eclipse.jdt.core.JavaIndexer, org.eclipse.emf.codegen.CodeGen,
org.eclipse.emf.codegen.JMerger, org.eclipse.emf.codegen.ecore.Generator,
org.eclipse.emf.importer.ecore.Ecore2GenModel,
org.eclipse.emf.importer.java.Java2GenModel,
org.eclipse.emf.importer.rose.Rose2GenModel.
at
org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:252)
at
org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:33)
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:401)
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:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:606)
at org.eclipse.equinox.launcher.Main.run(Main.java:1477)
at org.eclipse.equinox.launcher.Main.main(Main.java:1450)
seems to be a conflict with required versions. Logfile attached.
Version-Release number of selected component (if applicable):
eclipse-ecf-core.noarch
3.14.6-3.fc31
eclipse-egit.noarch
5.6.0-2.fc31
eclipse-emf-core.noarch
1:2.20.0-3.fc31
eclipse-emf-runtime.noarch
2.20.0-3.fc31
eclipse-emf-xsd.noarch
2.20.0-3.fc31
eclipse-equinox-osgi.x86_64
1:4.14-5.fc31
eclipse-gef.noarch
3.11.0-9.fc31
eclipse-jdt.noarch
1:4.14-5.fc31
eclipse-jgit.noarch
5.6.0-1.fc31
eclipse-m2e-core.noarch
1.11.0-1.fc31
eclipse-m2e-workspace.noarch
0.4.0-13.fc31
eclipse-nls-de.noarch
4.10.0-1.fc31
eclipse-p2-discovery.noarch
1:4.14-5.fc31
eclipse-pde.x86_64
1:4.14-5.fc31
eclipse-platform.x86_64
1:4.14-5.fc31
eclipse-swt.x86_64
1:4.14-5.fc31
eclipse-webtools-common.noarch
3.13.0-1.fc31
eclipse-webtools-servertools.noarch
3.13.0-1.fc31
eclipse-webtools-sourceediting.noarch
3.13.0-1.fc31
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1838330] New: Unable to install eclipse
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1838330
Bug ID: 1838330
Summary: Unable to install eclipse
Product: Fedora
Version: 31
Status: NEW
Component: eclipse
Assignee: mat.booth(a)redhat.com
Reporter: cquike(a)arcor.de
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:
Trying to install eclipse in a fresh fedora container with dnf fails:
# dnf install eclipse-platform
Last metadata expiration check: 0:14:08 ago on Wed May 20 22:15:50 2020.
Error:
Problem: conflicting requests
- package eclipse-platform-1:4.14-5.fc31.x86_64 requires glassfish-el >=
3.0.1, 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
- package glassfish-el-3.0.1-0.12.b08.module_f31+6519+12cd0b27.noarch is
filtered out by modular filtering
- package glassfish-el-3.0.1-0.12.b08.module_f31+6793+1c93c38e.noarch is
filtered out by modular filtering
- package glassfish-el-3.0.1-0.11.b08.fc31.noarch is filtered out by modular
filtering
I guess that enabling some module the dependency can be satisfied, but if I
understand modularity correctly only rpm from modules can depend on other
modules, right?
How reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1813168] New: Cannot install - broken dependencies
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1813168
Bug ID: 1813168
Summary: Cannot install - broken dependencies
Product: Fedora
Version: 31
Status: NEW
Component: eclipse-egit
Assignee: rob.myers(a)gtri.gatech.edu
Reporter: fedora(a)famillecollet.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, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com,
rob.myers(a)gtri.gatech.edu
Target Milestone: ---
Classification: Fedora
# dnf update --best
Error:
Problem: package eclipse-egit-5.6.0-2.fc31.noarch requires jgit >= 5.6.0, but
none of the providers can be installed
- cannot install the best update candidate for package
eclipse-egit-5.3.0-2.fc31.noarch
- package jgit-5.6.0-1.fc31.noarch is filtered out by modular filtering
Indeed, the modular repository provides jgit 5.4 (eclipse:2019-06) or jgit 5.5
(eclipse:latest)
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1801198] New: upgrade of eclipse-webtools-sourceediting is impossible due to conflicts
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1801198
Bug ID: 1801198
Summary: upgrade of eclipse-webtools-sourceediting is
impossible due to conflicts
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: eclipse-webtools
Severity: medium
Assignee: mat.booth(a)redhat.com
Reporter: R.Perdok(a)familieperdok.nl
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt,
mat.booth(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Eclipse-webtools-sourceediting cannot be updates due to a conflict
Version-Release number of selected component (if applicable):
Problem: package eclipse-pdt-6.2.0-3.fc31.noarch requires
osgi(org.eclipse.wst.jsdt.core), but none of the providers can be installed
- package eclipse-pdt-6.2.0-3.fc31.noarch requires
osgi(org.eclipse.wst.jsdt.ui), but none of the providers can be installed
- package eclipse-pdt-6.2.0-3.fc31.noarch requires
osgi(org.eclipse.wst.jsdt.web.core), but none of the providers can be installed
- package eclipse-pdt-6.2.0-3.fc31.noarch requires
osgi(org.eclipse.wst.jsdt.web.ui), but none of the providers can be installed
- cannot install both
eclipse-webtools-sourceediting-3.15.0-3.module_f31+7243+50fb5b11.noarch and
eclipse-webtools-sourceediting-3.15.0-1.module_f31+6793+1c93c38e.noarch
- cannot install both
eclipse-webtools-sourceediting-3.15.0-3.module_f31+7243+50fb5b11.noarch and
eclipse-webtools-sourceediting-3.15.0-1.module_f31+6519+12cd0b27.noarch
- cannot install the best update candidate for package
eclipse-webtools-sourceediting-3.15.0-1.module_f31+6793+1c93c38e.noarch
- cannot install the best update candidate for package
eclipse-pdt-6.2.0-3.fc31.noarch
- package eclipse-webtools-sourceediting-3.13.0-1.fc31.noarch is filtered out
by modular filtering
================================================================================================================================================================
Package Architecture Version
Repository Size
================================================================================================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
eclipse-webtools-sourceediting noarch
3.15.0-1.module_f31+6519+12cd0b27 fedora-modular
33 M
eclipse-webtools-sourceediting noarch
3.15.0-3.module_f31+7243+50fb5b11 updates-modular
12 M
Transaction Summary
================================================================================================================================================================
Skip 2 Packages
How reproducible:
run dnf update
Steps to Reproduce:
1.dnf update
2.
3.
Actual results:
Above error message
Expected results:
upgrade without error messages
Additional info:
Suggested options "--best --allowerasing" do not offer a solution.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Bug 1795038] New: Java/Eclipse packages (e.g. glassfish-jsp) are not being updated
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1795038
Bug ID: 1795038
Summary: Java/Eclipse packages (e.g. glassfish-jsp) are not
being updated
Product: Fedora
Version: 31
Status: NEW
Component: eclipse
Assignee: mat.booth(a)redhat.com
Reporter: jan.public(a)famvlug.nl
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
I have been using my system since many Fedora versions, and I always upgrade
Fedora when there is a new release.
It is possible that I have been fidling with my system to get Eclipse working.
At the moment, it seems that I have a modular Eclipse package:
# dnf list installed | grep eclipse-platform
eclipse-platform.x86_64
1:4.13-6.module_f31+7243+50fb5b11 @updates-modular
My system is fully up to date:
# dnf update
Last metadata expiration check: 2:19:18 ago on Sun 26 Jan 2020 14:03:38 CET.
Dependencies resolved.
Nothing to do.
Complete!
However according to dnf updateinfo info there are updates available:
[root@rainbowdash ~]# dnf updateinfo info
Last metadata expiration check: 2:19:53 ago on Sun 26 Jan 2020 14:03:38 CET.
===============================================================================
apache-commons-compress-1.19-1.fc31
===============================================================================
Update ID: FEDORA-2019-da0eac1eb6
Type: security
Updated: 2020-01-25 06:59:21
Bugs: 1761797 - CVE-2019-12402 apache-commons-compress: denial of
service vulnerability
Description: Update to version 1.19.
:
: Resolves CVE-2019-12402.
Severity: Important
===============================================================================
eclipse-m2e-workspace-0.4.0-13.fc31
===============================================================================
Update ID: FEDORA-2019-d3d3a793c2
Type: enhancement
Updated: 2020-01-25 06:54:44
Description: Fix build to avoid takari-* stack
Severity: Low
===============================================================================
glassfish-hk2-2.5.0-5.fc31
===============================================================================
Update ID: FEDORA-2019-a0e393f792
Type: bugfix
Updated: 2020-01-25 06:59:52
Bugs: 1735263 - glassfish-hk2: FTBFS in Fedora rawhide/f31
Description: Rebuild with reduced dependency set to fix FTBFS on fedora 31+.
Severity: None
===============================================================================
glassfish-jsp-2.3.4-2.fc31 takari-polyglot-0.4.4-5.fc31
===============================================================================
Update ID: FEDORA-2019-45dcf79c41
Type: enhancement
Updated: 2020-01-04 21:32:10
Description: Unretirement of glassfish-jsp and takari-polyglot.
:
Severity: Low
===============================================================================
jackson-annotations-2.10.0-1.fc31 jackson-bom-2.10.0-1.fc31
jackson-core-2.10.0-1.fc31 jackson-databind-2.10.0-1.fc31
jackson-parent-2.10-1.fc31
===============================================================================
Update ID: FEDORA-2019-cf87377f5f
Type: security
Updated: 2020-01-25 06:58:04
Bugs: 1755832 - CVE-2019-16335 jackson-databind: polymorphic typing
issue related to com.zaxxer.hikari.HikariDataSource [fedora-all]
: 1755850 - CVE-2019-14540 jackson-databind: polymorphic typing
issue related to com.zaxxer.hikari.HikariConfig [fedora-all]
: 1758168 - jackson-databind: Serialization gadgets in classes of
the ehcache package [fedora-all]
: 1758172 - jackson-databind: Serialization gadgets in classes of
the commons-configuration package [fedora-all]
: 1758183 - jackson-databind: Serialization gadgets in classes of
the xalan package [fedora-all]
: 1758188 - CVE-2019-16942 jackson-databind: Serialization gadgets
in classes of the commons-dbcp package [fedora-all]
: 1758193 - CVE-2019-16943 jackson-databind: Serialization gadgets
in classes of the p6spy package [fedora-all]
Description: - Update jackson-parent to version 2.10.
: - Update jackson-bom to version 2.10.0.
: - Update jackson-annotations to version 2.10.0.
: - Update jackson-core to version 2.10.0.
: - Update jackson-databind to version 2.10.0.
:
: Resolves CVE-2019-14540, CVE-2019-16335, CVE-2019-16942,
CVE-2019-16943.
Severity: Moderate
===============================================================================
jackson-dataformat-xml-2.10.0-1.fc31 jackson-jaxrs-providers-2.10.0-1.fc31
jackson-modules-base-2.10.0-1.fc31 stax2-api-4.2-1.fc31
woodstox-core-6.0.2-1.fc31
===============================================================================
Update ID: FEDORA-2019-12ea5e5227
Type: enhancement
Updated: 2020-01-25 06:57:05
Description: Update resteasy dependencies
Severity: None
===============================================================================
kernel-5.4.13-201.fc31
===============================================================================
Update ID: FEDORA-2020-aa144b34ed
Type: bugfix
Updated: 2020-01-25 06:59:26
Description: Update to Linux v5.4.13
Severity: None
===============================================================================
maven-3.5.4-13.fc31
===============================================================================
Update ID: FEDORA-2019-f3a7f84557
Type: bugfix
Updated: 2020-01-25 06:56:53
Bugs: 1767329 - postun scriplet failure
Description: Fix broken postun scriptlet.
Severity: None
===============================================================================
maven-osgi-0.2.0-18.fc31
===============================================================================
Update ID: FEDORA-2019-6ff5c442a3
Type: unknown
Updated: 2020-01-25 06:57:02
Description: Package un-retirement.
Severity: None
Note that glassfish-jsp-2.3.4-2.fc31 was already updated in the repository on
2020-01-04 21:32:10 according to the dnf updateinfo output.
Here for information the output of a few commands:
# dnf list installed | grep glassfish-jsp
glassfish-jsp.noarch
2.3.3-0.14.b02.module_f31+6793+1c93c38e @updates-modular
glassfish-jsp-api.noarch
2.3.3-1.module_f31+7243+50fb5b11 @updates-modular
# dnf module list | grep glassfish-jsp
<no results here>
# dnf install glassfish-jsp
Last metadata expiration check: 2:25:20 ago on Sun 26 Jan 2020 14:03:38 CET.
Package glassfish-jsp-2.3.3-0.14.b02.module_f31+6793+1c93c38e.noarch is already
installed.
Dependencies resolved.
Nothing to do.
Complete!
# dnf remove glassfish-jsp
This results in the removal of 134 packages, including eclipse modular. I did
not proceed with this removal.
Is there a problem with the unretirement of glassfish-jsp?
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[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