Bug 173039
| Summary: | Eclipse 3.1.1 fails to start up | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dawid Zamirski <dzrudy> | ||||
| Component: | eclipse | Assignee: | Andrew Overholt <overholt> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2005-11-14 19:27:01 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Dawid Zamirski
2005-11-12 21:41:17 UTC
Created attachment 120990 [details]
Startup log
(In reply to comment #0) > Since I've upgraded eclipse to the newet version (3.1.1), it doesn't startup > anymore. The version that was in updates-testing (same release as in official > updates) was starting up and woking I don't understand. If you had the version that *was* in updates testing, there should not have been anything to upgrade once that update went final because it is the exact same. > execpt software updates. > Once the rpm has been posted to the updates channel, I removed the testing > version and replaced with the one from the official repo. Why did you do this? How did you remove the first set of RPMs? > After the update, albeit the same version tag, it doesn't statrup (errors in > attached log file). Removing ~/.eclipse and /usr/share/eclipse and all > plugins doesn't help. You shouldn't need to remove /usr/share/eclipse if you remove all the RPMs (don't forget about libswt3-gtk2). What is the difference between removing the RPMs and removing "all plugins"? > [maners@athlon64 ~]$ rpm -qa | grep gcj > [...] > java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.1 > java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.2 > java-1.4.2-gcj-compat-devel-1.4.2.0-40jpp_31rh.FC4.2 > libgcj-4.0.1-4.fc4 > java-1.4.2-gcj-compat-src-1.4.2.0-40jpp_31rh.FC4.2 > libgcj-4.0.1-4.fc4 Why are things showing up twice? Perhaps your update of gcc* (including *gcj*) did not update finish correctly? What do you get when you run: java -version gcj --version gcc --version ? Are you familiar with the alternatives system? I think you might have your alternatives set up incorrectly. Let's determine what version(s) of gij/gcj you have first and go from there. > [maners@athlon64 ~]$ rpm -qa | grep java > [...] > xerces-j2-javadoc-impl-2.6.2-4jpp_5fc > oro-javadoc-2.0.8-2jpp While I think this is probably inconsequential and unrelated to your current problem, you do have packages that are part of JPackage but not part of FC. > [maners@athlon64 ~]$ rpm -qa | grep eclipse > eclipse-ecj-3.1.1-1jpp_1fc.FC4.4 > eclipse-rcp-3.1.1-1jpp_1fc.FC4.4 > eclipse-platform-3.1.1-1jpp_1fc.FC4.4 Okay. Do you also have libswt3-gtk2? Are you perhaps running the 32-bit gcc* on x86_64 but attempting to run the 64-bit Eclipse? That will not work. You can see by doing: rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n" | grep gcj rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n" | egrep "eclipse|swt" > I don't understand. If you had the version that *was* in updates testing, > there should not have been anything to upgrade once that update went final > because it is the exact same. I was aware that the package from testing is the same as in official updates, and of course, it didn't show up as update. I just wanted to make sure that my rpm comes from official updates channel (it might not make much of a sense, but I feel mentally better when the package comes form official updates :-P) What I did was yum remove eclipse-platform and any other packages with "eclipse" in its name. Then I installed it with yum again with updates-testing disabled. > You shouldn't need to remove /usr/share/eclipse if you remove all the RPMs > (don't forget about libswt3-gtk2). What is the difference between removing > the RPMs and removing "all plugins"? At my first attempt I didn't remove any files manually, but since eclipse didn't start I removed the rpms again and then any left overs from previous install (~/.eclipse and /usr/share/eclipse). I had some plugins that I installed manually (PHPEclipse, JScipt etc) that I extracted to /usr/share/eclipse adnthey worked fine with 3.0 M6 (I didn't know at that time about ~/.eclipse directory) Therfore I thought that some of them migh cause the failure and for that reason I removed /usr/share/eclipse manually after rpm unistall. > Why are things showing up twice? Perhaps your update of gcc* (including > *gcj*) did not update finish correctly? What do you get when you run: <snip> Well, I don't know why they are showing up twice (both seem to be x84_64) and I think it might be the result of playing with smartpm some time ago. [maners@athlon64 ~]$ java --version java version "1.4.2" gij (GNU libgcj) version 4.0.1 20050727 (Red Hat 4.0.1-5) [maners@athlon64 ~]$ gcj --version gcj (GCC) 4.0.1 20050727 (Red Hat 4.0.1-5) [maners@athlon64 ~]$ gcc --version gcc (GCC) 4.0.1 20050727 (Red Hat 4.0.1-5) [maners@athlon64 ~]$ rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n" | grep gcj libgcj-devel-4.0.1-4.fc4.x86_64 libgcj-src-4.0.1-4.fc4.x86_64 java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.1.x86_64 java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.2.x86_64 java-1.4.2-gcj-compat-devel-1.4.2.0-40jpp_31rh.FC4.2.x86_64 libgcj-4.0.1-4.fc4.x86_64 java-1.4.2-gcj-compat-src-1.4.2.0-40jpp_31rh.FC4.2.x86_64 libgcj-4.0.1-4.fc4.i386 [maners@athlon64 ~]$ rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n" | egrep "eclipse|swt" libswt3-gtk2-3.1.1-1jpp_1fc.FC4.4.x86_64 eclipse-ecj-3.1.1-1jpp_1fc.FC4.4.x86_64 eclipse-rcp-3.1.1-1jpp_1fc.FC4.4.x86_64 eclipse-platform-3.1.1-1jpp_1fc.FC4.4.x86_64 I'll remove the duplicated packages and will see if it helps It seems that I have something broken with my rpm pakcages. When I try to remove any of the duplicated java-1.4.2-gcj-compat packages I get scriptlet error: [root@athlon64 ~]# rpm -e java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.1 /var/tmp/rpm-tmp.75084: line 8: /usr/bin/rebuild-security-providers: No such file or directory error: %postun(java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.1.x86_64) scriptlet failed, exit status 127 Ok, now it works! :-) The problem was caused by jpackage-utils-1.6.5 that I had installed which probably came form JPackage repo. I removed it and installed the 1.6.3 which is in official fedora repository and this solved the scriptlet error. After reinstaling all the packages, it works fine. Thank You. (In reply to comment #5) > Ok, now it works! :-) The problem was caused by jpackage-utils-1.6.5 that I had > installed which probably came form JPackage repo. I removed it and installed the > 1.6.3 which is in official fedora repository and this solved the scriptlet > error. After reinstaling all the packages, it works fine. Thank You. Phew! That's good news. Nice working tracking that down :) |