https://bugzilla.redhat.com/show_bug.cgi?id=1197661
Bug ID: 1197661
Summary: eclipse's editor smudges on scrolling
Product: Fedora
Version: 22
Component: eclipse
Severity: high
Assignee: akurtako(a)redhat.com
Reporter: peljasz(a)yahoo.co.uk
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, msimacek(a)redhat.com,
overholt(a)gmail.com, rgrunber(a)redhat.com,
swagiaal(a)redhat.com
Created attachment 997017
--> https://bugzilla.redhat.com/attachment.cgi?id=997017&action=edit
smudged editor
Description of problem:
sometimes editor gets smudged after scrolling, I have to click to get focus
back to editor for the smudges to refresh and dissapear.
Version-Release number of selected component (if applicable):
eclipse-platform-4.4.1-17.fc22.x86_64
mesa-dri-drivers-10.5.0-1.20150218.fc22.x86_64
mesa-filesystem-10.5.0-1.20150218.fc22.x86_64
mesa-libEGL-10.5.0-1.20150218.fc22.i686
mesa-libEGL-10.5.0-1.20150218.fc22.x86_64
mesa-libEGL-devel-10.5.0-1.20150218.fc22.x86_64
mesa-libgbm-10.5.0-1.20150218.fc22.i686
mesa-libgbm-10.5.0-1.20150218.fc22.x86_64
mesa-libGL-10.5.0-1.20150218.fc22.i686
mesa-libGL-10.5.0-1.20150218.fc22.x86_64
mesa-libglapi-10.5.0-1.20150218.fc22.i686
mesa-libglapi-10.5.0-1.20150218.fc22.x86_64
mesa-libGL-devel-10.5.0-1.20150218.fc22.x86_64
mesa-libGLES-10.5.0-1.20150218.fc22.x86_64
mesa-libGLU-9.0.0-7.fc22.x86_64
mesa-libGLU-devel-9.0.0-7.fc22.x86_64
mesa-libOpenCL-10.5.0-1.20150218.fc22.x86_64
mesa-libwayland-egl-10.5.0-1.20150218.fc22.x86_64
mesa-libxatracker-10.5.0-1.20150218.fc22.x86_64
mesa-vdpau-drivers-10.5.0-1.20150218.fc22.x86_64
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.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=NEOvsxUz2o&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1245759
Bug ID: 1245759
Summary: Attach-process does not work. "ptrace: Operation not
permitted"
Product: Fedora
Version: 22
Component: eclipse-cdt
Assignee: jjohnstn(a)redhat.com
Reporter: lufimtse(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, krzysztof.daniel(a)gmail.com,
rgrunber(a)redhat.com
Description of problem:
As of F22, in Eclipse-CDT, you can't debug via "attach to process".
When you try, nothing happens.
When trying the same thing with GDB, you get an error:
"ptrace: Operation not permitted."
After some troubleshooting, one workaround is:
sudo chmod +s /usr/bin/gdb
The root cause of the issue has been narrowed down to a security hardening in:
https://bugzilla.redhat.com/show_bug.cgi?id=1209492
I tested one potential patch and it fixed the issue.
But at present there is a debate about security in the bug above (50
comments..).
- The Security-hardening argument is that ptrace has the ability to look into
the memory of any process, thus being a security threat.
- The usability argument is that the change is security theater. It only
breaks a lot of applications and doesn't really add much security since there
are other easier ways to do the same (e.g core dumping another application and
reading the dump). As such it's fixing something that isn't broken but causes
breakage in many other apps.
This bug is a tracker bug. It is intended to raise attention that the
security-hardening change (in bug 1209492) breaks Eclipse-cdt's
attach-to-process functionality and imho should be reversed. To me it seems
that this is an unnecessary a big wall that can be easily walked around anyway.
Version-Release number of selected component (if applicable):
F22. Eclipse independent.
How reproducible:
Always
Steps to Reproduce:
- Start a C application. (e.g a JVM).
- From Eclipse, attempt to attach to the process.
Actual results:
- Nothing happens
Expected results:
- Debug session should have started.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=S1A6UfYuFR&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1223946
Bug ID: 1223946
Summary: History not available in jgit
Product: Fedora
Version: 22
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: krzysztof.daniel(a)gmail.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,
swagiaal(a)redhat.com
Created attachment 1028352
--> https://bugzilla.redhat.com/attachment.cgi?id=1028352&action=edit
screenshot
Eclipse GTK3 does not show history. It is there, but disappears once scroll is
shown.
workaround:
1. switch to ugly gtk2
2. resize the view to remove scroll
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=sbCxzn5rkT&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1206893
Bug ID: 1206893
Summary: Binary blobs in upstram tarball we build from
Product: Fedora
Version: rawhide
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: praiskup(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, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, msimacek(a)redhat.com,
rgrunber(a)redhat.com, swagiaal(a)redhat.com
I can see that output of the following command is not empty:
tar tf R4_platform-aggregator-I20150317-2000.tar.xz \
| grep -e \\.jar$ -e \\.njar$
Do you think that we could call something like:
find -delete -name '*.jar' -o -name '*.njar' -o -name '*.class'
.. somewhere early in %prep phase, as soon as the tarballs are extracted?
That would kind of work-around our guarantees that we don't build from hacked
binary blobs.
I was unable to check whether those binary files are actually used
because the eclipse package fails to build in my mock profile even if I do not
edit it. However, if those actually are used - it would be probably serious
packaging problem against our Java PG.
(background story: I tried to resolve similar problems in my package and I
picked eclipse randomly as typical java package I should learn from, but
found similar issues)
Pavel
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=PrN4W1NzXm&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1208483
Bug ID: 1208483
Summary: eclipse does not build on ppc64/s390(x)
Product: Fedora
Version: 22
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: than(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, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, msimacek(a)redhat.com,
rgrunber(a)redhat.com, swagiaal(a)redhat.com
eclipse doesn't build on because of missing dependencies.
DEBUG util.py:391: Error: No Package found for eclipse-ecf-core >= 3.9.2-2
DEBUG util.py:391: Error: No Package found for eclipse-emf-core >= 1:2.10.2-1
DEBUG util.py:391: Error: No Package found for
osgi(org.eclipse.jetty.continuation) >= 9.2.9
DEBUG util.py:391: Error: No Package found for osgi(org.eclipse.jetty.http) >=
9.2.9
DEBUG util.py:391: Error: No Package found for osgi(org.eclipse.jetty.io) >=
9.2.9
DEBUG util.py:391: Error: No Package found for
osgi(org.eclipse.jetty.security) >= 9.2.9
DEBUG util.py:391: Error: No Package found for osgi(org.eclipse.jetty.server)
>= 9.2.9
DEBUG util.py:391: Error: No Package found for osgi(org.eclipse.jetty.servlet)
>= 9.2.9
DEBUG util.py:391: Error: No Package found for osgi(org.eclipse.jetty.util) >=
9.2.9
for more infos please take a look at:
http://ppc.koji.fedoraproject.org/kojifiles/work/tasks/8680/2408680/root.log
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=tosLNdZf3j&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1217134
Bug ID: 1217134
Summary: eclipse-ecf does not build on ppc64/s390(x)
Product: Fedora
Version: 22
Component: eclipse-ecf
Assignee: akurtako(a)redhat.com
Reporter: than(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com, rgrunber(a)redhat.com
rpmbuild --rebuild eclipse-ecf-3.9.3-1.fc22.src.rpm has failed on ppc64/s390(x)
looking at the build.log, the genericTargets.xml is searched in nonexistent
directory
customTargets.xml:19: The following error occurred while executing this line:
java.io.FileNotFoundException:
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
(No such file or directory)
build.log
---------
BUILD FAILED
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/scripts/build.xml:35:
The following error occurred while executing this line:
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/scripts/build.xml:91:
The following error occurred while executing this line:
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/templates/package-build/customTargets.xml:19:
The following error occurred while executing this line:
java.io.FileNotFoundException:
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.9.0.v20150120-1031/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
(No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:250)
at
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:178)
at
org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:392)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:34)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:34)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441)
at
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:566)
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:497)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:511)
at org.eclipse.ant.core.AntRunner.start(AntRunner.java:607)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
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:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
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:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
at org.eclipse.core.launcher.Main.main(Main.java:34)
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=s72CHHmE7C&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1247118
Bug ID: 1247118
Summary: jetty8: FTBFS in rawhide
Product: Fedora
Version: rawhide
Component: jetty8
Assignee: msimacek(a)redhat.com
Reporter: mizdebsk(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msimacek(a)redhat.com,
msrb(a)redhat.com, pmackinn(a)redhat.com
Description of problem:
Package jetty8 fails to build from source in rawhide.
Version-Release number of selected component (if applicable):
8.1.17-1.fc23
Steps to Reproduce:
koji build --scratch f24 jetty8-8.1.17-1.fc23.src.rpm
Additional info:
This package is tracked by Koschei. See:
https://apps.fedoraproject.org/koschei/package/jetty8
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=8wnwfzMRRK&a=cc_unsubscribe