<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 5/31/2010 5:08 PM, Casimiro de Almeida Barreto wrote:
<blockquote cite="mid:4C03C2F5.20208@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
Em 31-05-2010 09:33, Andrew Overholt escreveu:
<blockquote cite="mid:20100531123304.GB2576@redhat.com" type="cite">
<pre wrap="">Hi Casimiro,
</pre>
<blockquote type="cite">
<pre wrap="">I've got the following problem with eclipse after update to F13: upon launch it
freezes at initial banner & uses about 80% of CPU time.
</pre>
</blockquote>
<pre wrap="">Please file a bug at bugzilla.redhat.com and we can work through it there.
Thanks,
Andrew
</pre>
</blockquote>
Hello,<br>
<br>
Apparently I have the problem solved. First of all, the listing had all
that modules because when eclipse refused to start I assumed something
was lacking and behave just like a n00b (yum install "eclipse-*" kind
of thing). So, it happened prior of having all those modules installed.
Anyways, what I did was to uninstall eclipse & everything related,
to remove .eclipse and workspace (inherited from F12), re-install
eclipse and bring back old content. And it worked.<br>
<br>
Apparently it was a problem with what was before & what was
updated. As error cannot be reproduced there's little sense in filling
a bug.<br>
</blockquote>
yes there is a reason to file the bug report. The upgrade should have
been seamless. Something like this has happened to many people on many
eclipse updates. Maybe there is something in your scenario that would
give the maintainer a clue. At worst, the bug will be closed as
insufficient information.<br>
</body>
</html>