https://bugzilla.redhat.com/show_bug.cgi?id=1249294
Fedora End Of Life <jkurik(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |EOL
Last Closed| |2016-07-19 13:18:20
--- Comment #15 from Fedora End Of Life <jkurik(a)fedoraproject.org> ---
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1246467
Bug ID: 1246467
Summary: cdtdebug: in F22, YAMA disallows ptrace, gdb attach
fails and the CDT UI does not report that to user
Product: Fedora
Version: 22
Component: eclipse-cdt
Assignee: jjohnstn(a)redhat.com
Reporter: mstahl(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:
in Fedora 22, YAMA disallows ptrace, gdb attach fails and the CDT UI does not
report that to user.
Version-Release number of selected component (if applicable):
gdb-7.9.1-17.fc22.x86_64
eclipse-platform-4.4.2-6.fc22.x86_64
eclipse-cdt-parsers-8.6.0-2.fc22.x86_64
eclipse-valgrind-3.2.0-1.fc22.noarch
eclipse-jdt-4.4.2-6.fc22.x86_64
eclipse-cdt-8.6.0-2.fc22.x86_64
eclipse-linuxtools-3.2.0-1.fc22.noarch
How reproducible:
by default in Fedora 22, YAMA disallows ptrace:
> cat /proc/sys/kernel/yama/ptrace_scope
1
Steps to Reproduce:
1. run "cdtdebug"
2. hit F11 to debug
3. select some process running under your UID to attach
Actual results:
attaching to process silently fails.
only if you switch to the "GDB traces" console you can see this:
384,219 18-target-attach --thread-group i1 6638
384,220 18^error,msg="ptrace: Operation not permitted."
Expected results:
Qt Creator handles this failure better, it pops up a dialog that says:
ptrace: Operation not permitted.
Could not attach to the process. Make sure no other debugger traces this
process.
If your uid matches the uid
of the target process, check the settings of
/proc/sys/kernel/yama/ptrace_scope
For more details, see /etc/sysctl.d/10-ptrace.conf
Additional info:
there is a bug about the YAMA default setting:
https://bugzilla.redhat.com/show_bug.cgi?id=1209492
--
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=QDrQ4MorRY&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1232094
Bug ID: 1232094
Summary: Some visual elements like trees and list disappear
Product: Fedora
Version: 22
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: bill_chatfield(a)yahoo.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
Created attachment 1039243
--> https://bugzilla.redhat.com/attachment.cgi?id=1039243&action=edit
Shows blank view contents where the Package Explorer tree and Palette contents
should be
Description of problem:
I'm attaching an image that shows this problem. The contents of the Package
Explorer tree disappears. The contents of the Palette view disappears.
Version-Release number of selected component (if applicable):
All components are standard Fedora 22 components updated to the latest version
available. Also the latest (23.0.6.172051) Android tools/SDK/plugins
(everything necessary for Android development) are installed.
How reproducible:
Steps to Reproduce:
1. Install all the Android development components into Eclipse.
2. Load a layout XML file, which shows a graphical picture of the Android
device screen, in the default editor in Eclipse (Android Common XML Editor).
3. Click around on various UI components
Actual results: The tree view in the Package Explorer disappears. The Outline
view contents disappear. The contents of the Palette view disappears.
Expected results: No UI component disappears.
Additional info:
If you move your mouse over the missing elements they reappear as you move over
each one.
--
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=9kF1mMj7zg&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1357271
Bug ID: 1357271
Summary: eclipse does not start
Product: Fedora
Version: 24
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: jan.kratochvil(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, rgrunber(a)redhat.com
Created attachment 1180777
--> https://bugzilla.redhat.com/attachment.cgi?id=1180777&action=edit
/home/lace/workspace/.metadata/.log
Description of problem:
Eclipse fails to start. I believe it will start on a fresh Fedora 24 x86_64
installation, my installation is an in-place upgrade for many Fedora releases
but it still should work I guess.
Version-Release number of selected component (if applicable):
eclipse-platform-4.6.0-0.6.git201605092000.fc24.x86_64
freemarker-2.3.23-2.fc24.noarch
How reproducible:
Always.
Steps to Reproduce:
rm -rf ~/workspace ~/.eclipse;eclipse
Actual results:
It asks for the workspace directory.
An error has occured. See the log file /home/lace/workspace/.metadata/.log.
Expected results:
Started Eclipse.
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=1352985
--- Comment #3 from Alexander Kurtakov <akurtako(a)redhat.com> ---
IIRC this is only for the previous release, aka v4 indexes could be read with
these but not v3 (which upstream still uses and generates).
We should not support multiple versoins but mylyn code has to be patched to
recreate a v5 index in this case instead of throwing an error. I think that
Sopot's platform patch does this already.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1352985
--- Comment #2 from Roland Grunberg <rgrunber(a)redhat.com> ---
It seems we do ship lucene-backward-codecs as a subpackage so I guess the
question becomes whether we want to support backward compatibility of indices.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1327642
Bug ID: 1327642
Summary: The encoding found: >>utf-8-<< on
/usr/lib/python2.7/site-packages/git/compat.py is not
a valid encoding.
Product: Fedora
Version: 23
Component: eclipse-pydev
Assignee: akurtako(a)redhat.com
Reporter: robinlee.sysu(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, npmccallum(a)redhat.com
Version-Release number of selected component:
eclipse-pydev-4.5.3-1.fc23
Additional info:
reporter: libreport-2.6.4
cmdline: /usr/bin/java -Xms128m -Xmx1024m
-Dorg.eclipse.swt.browser.UseWebKitGTK=true -Dhelp.lucene.tokenizer=standard
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
-XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init>
-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates,instantiateTemplate
-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage,addBinding
-XX:CompileCommand=exclude,org/python/pydev/editor/codecompletion/revisited/PythonPathHelper,isValidSourceFile
-XX:CompileCommand=exclude,org/eclipse/tycho/core/osgitools/EquinoxResolver,newState
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins
-Dp2.fragments=/usr/share/eclipse/droplets,/usr/lib64/eclipse/droplets
-Declipse.p2.skipMovedInstallDetection=true -jar
/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.100.v20160304-1300.jar
-os linux -ws gtk -arch x86_64 -showsplash
/usr/lib64/eclipse//plugins/org.eclipse.platform_4.5.2.v20160304-1300/splash.bmp
-launcher /usr/lib64/eclipse/eclipse -name Eclipse --launcher.library
/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.300.v20160304-1300/eclipse_1613.so
-startup
/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.100.v20160304-1300.jar
-protect master --launcher.appendVmargs -exitdata ff800d -vm /usr/bin/java
-vmargs -Xms128m -Xmx1024m -Dorg.eclipse.swt.browser.UseWebKitGTK=true
-Dhelp.lucene.tokenizer=standard
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
-XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init>
-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates,instantiateTemplate
-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage,addBinding
-XX:CompileCommand=exclude,org/python/pydev/editor/codecompletion/revisited/PythonPathHelper,isValidSourceFile
-XX:CompileCommand=exclude,org/eclipse/tycho/core/osgitools/EquinoxResolver,newState
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins
-Dp2.fragments=/usr/share/eclipse/droplets,/usr/lib64/eclipse/droplets
-Declipse.p2.skipMovedInstallDetection=true -jar
/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.100.v20160304-1300.jar
eclipseplugin: org.python.pydev.shared_core
executable:
/usr/lib64/eclipse/dropins/pydev-core/eclipse/plugins/org.python.pydev.shared_core_4.5.3.201601221600
kernel: 4.4.6-300.fc23.x86_64
runlevel: N 5
type: libreport
uid: 1000
Truncated backtrace:
java.io.UnsupportedEncodingException: The encoding found: >>utf-8-<< on
/usr/lib/python2.7/site-packages/git/compat.py is not a valid encoding.
at
org.python.pydev.shared_core.io.FileUtils.getValidEncoding(FileUtils.java:728)
at
org.python.pydev.shared_core.io.FileUtils.getPythonFileEncoding(FileUtils.java:689)
at
org.python.pydev.shared_core.io.FileUtils.getPythonFileEncoding(FileUtils.java:759)
at
org.python.pydev.core.FileUtilsFileBuffer.getCustomReturnFromFile(FileUtilsFileBuffer.java:155)
at
com.python.pydev.analysis.additionalinfo.AbstractAdditionalTokensInfo.addAstInfo(AbstractAdditionalTokensInfo.java:281)
at
com.python.pydev.analysis.additionalinfo.AbstractAdditionalInfoWithBuild.restoreInfoForModuleManager(AbstractAdditionalInfoWithBuild.java:258)
at
com.python.pydev.analysis.additionalinfo.AdditionalSystemInterpreterInfo.recreateAllInfo(AdditionalSystemInterpreterInfo.java:179)
at
com.python.pydev.analysis.additionalinfo.AdditionalSystemInterpreterInfo.getAdditionalSystemInfo(AdditionalSystemInterpreterInfo.java:155)
at
com.python.pydev.analysis.additionalinfo.AdditionalSystemInterpreterInfo.getAdditionalSystemInfo(AdditionalSystemInterpreterInfo.java:124)
at
com.python.pydev.analysis.additionalinfo.AdditionalSystemInterpreterInfo.recreateAllInfo(AdditionalSystemInterpreterInfo.java:171)
at
com.python.pydev.analysis.additionalinfo.builders.InterpreterObserver.notifyDefaultPythonpathRestored(InterpreterObserver.java:35)
at
org.python.pydev.ui.interpreters.AbstractInterpreterManager.restorePythopathForInterpreters(AbstractInterpreterManager.java:726)
at
org.python.pydev.ui.interpreters.AbstractInterpreterManager.setInfos(AbstractInterpreterManager.java:643)
at
org.python.pydev.ui.pythonpathconf.AutoConfigMaker$1.run(AutoConfigMaker.java:137)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1339362
Bug ID: 1339362
Summary: Please unbundle pep8 and lib2to3
Product: Fedora
Version: 24
Component: eclipse-pydev
Severity: low
Assignee: akurtako(a)redhat.com
Reporter: rhbz(a)genodeftest.de
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jjohnstn(a)redhat.com, npmccallum(a)redhat.com
Description of problem:
Currently, eclipse-pydev bundles a bunch of files in
/usr/lib64/eclipse/droplets/pydev-core/eclipse/plugins/org.python.pydev_5.0.0.201605181100/pysrc/third_party,
notably a folder named pep8 containing pep8.py and autopep8.py and a sub folder
named lib2to3. All those files are provided by their respective packages:
python-pep8, python3-pep8
python-autopep8, python3-autopep8
lib2to3 stuff is included in python standard library, python{2/3}-future and
python3-modernize.
According to the packaging guidelines [1], libraries should not be bundled in
rpm packages.
Version-Release number of selected component (if applicable):
5.0.0-1.fc24
How reproducible:
always due to packaging
[1]
https://fedoraproject.org/wiki/Packaging:Guidelines#Bundling_and_Duplicatio…
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1352985
--- Comment #1 from Roland Grunberg <rgrunber(a)redhat.com> ---
Easy workaround was to delete .taskListIndex/ folder from the mylyn task data
storage location. For most users this will probably be in
$WORKSAPCE/.metadata/.mylyn/.taskListIndex/ assuming they usd the default
location. The index seems to have been re-built and the error no longer occurs.
I'm fine with having this be the workaround, given that lucene may from time to
time offer backward compatibility into bundles we don't/can't ship.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1352983
--- Comment #1 from Roland Grunberg <rgrunber(a)redhat.com> ---
The InstalledSoftwarePage creates a viewer using InstalledIUGroup, and the
input content is supplied by ProfileElement, which simply wraps the current p2
Profile within the profile registry.
The p2 Profile will have listings for all bundles (which is likely why the
plugins tab lists droplets), but the droplet solution as a whole doesn't add
any features or feature groups to the profile.
If we add this functionality it seems like the best way to do it is to extend
ProfileElement to handle features from droplet locations and change the input
element passed in by InstalledIUGroup to that new class.
--
You are receiving this mail because:
You are on the CC list for the bug.