Red Hat Bugzilla – Bug 161518
cvs repository exploring perspective throws exception browsing cvs.gnome.org
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
This is a fresh install of FC4 and Eclipse, no workspace or anything. I used the CVS Repository Exploring perspective, and added a new repository: anoncvs.gnome.org/pserver/anonymous , then clicked on "HEAD". Eclipse showed about a fifth perhaps of the list, then threw an exception, and failed to show the remainder. I'll attach the output from ~/workspace/.metadata/.log
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start Eclipse
2. Add new repostory with host: anoncvs.gnome.org method: pserver username: anonymous
3. Click HEAD
Created attachment 115905 [details]
I've never seen this type of behaviour. Before I tell you to upgrade to what's
in rawhide (or wait for 3.1 final next week - I'll be doing an FC4 update then),
try rm -rf ~/.eclipse and try again. There always seem to be problems with
~/.eclipse when moving between versions and/or JVMs.
I'm getting exactly the same error with 3.1.0_fc-0.M6.22. Even when I 'rm -rf
~/.eclipse' this issue persists.
I just tried to reproduce this bug with the proposed FC4 update (in
updates-testing) but I cannot. If you can try out this update  and verify
that this issue is indeed fixed, I would appreciate it.
yum --enablerepo=updates-testing update eclipse-pde (or whatever)
Seems to be working now for me on the latest version of Eclipse 3.1.1 downloaded
from the FC4 repo.
Now I seem to be getting an NPE when I attempt to read information using extssh.
Not sure if it is related to this bug or a seperate issue (see attached
Created attachment 120982 [details]
(In reply to comment #6)
> Now I seem to be getting an NPE when I attempt to read information using extssh.
> Not sure if it is related to this bug or a seperate issue (see attached
That's a separate issue: bug 146782.
Can we close this?
Closing due to lack of response.