| Summary: | Can't start eclipse | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jan Pihlgren <jan> |
| Component: | RPM Packages | Assignee: | D Morgan <dmorganec> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | andr999 |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | eclipse | CVE: | |
| Status comment: | |||
|
Description
Jan Pihlgren
2012-06-04 10:29:50 CEST
what is the output of java -version ? can you try what is written ? try "ulimit -c unlimited" before starting Java again then *attachù the log Source RPM:
(none) =>
eclipse After an update, a few days ago, I have "java-1.7.0-openjdk" version 1.7.0.3 2.2.1.0.2.mga2 x86-64. Now Eclipse start. Message: [jan@localhost Script]$ eclipse CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith CompilerOracle: exclude org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.<init> CompilerOracle: exclude org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate CompilerOracle: exclude org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding CompilerOracle: exclude org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile CompilerOracle: exclude org/python/pydev/ui/filetypes/FileTypesPreferencesPage.getDottedValidSourceFiles [jan@localhost Script]$ When I try to change workspace I get the same error as before. Mijnor difference in messages: # JRE version: 7.0_03 # Java VM: OpenJDK 64-Bit Server VM (23.0-b21 mixed mode linux-amd64 compressed oops) I don't understand this "try "ulimit -c unlimited" before starting Java again"?
David Walser
2012-09-07 17:56:15 CEST
Assignee:
bugsquad =>
dmorganec First he wanted you to type "java --version" in a console to show what version of java you were using. (Which you listed in your last message.) After, what was meant is 1) open a console, 2) then type "ulimit -c unlimited" (without quotes) this is suggested in the error message of your first post. It removes any limits on the size of error log files. 3) then try to start eclipse (and java) again. 4) after getting an error again, use the "add an attachment" link just above your first post to send the error log. CC:
(none) =>
andre999mga is this bug still valid on cauldron ? Cauldron? That's for Mageia 4 Alpha 2? Eclipse not in the repositories and not possible to install. In Mageia 3 Eclipse start. I don't understand the question. i just messed up the versions :) This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |