Bug 207215 - Can't open cvs perspecive after creating new workspace
Can't open cvs perspecive after creating new workspace
Status: CLOSED DUPLICATE of bug 202081
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ben Konrath
Depends On:
  Show dependency treegraph
Reported: 2006-09-19 18:53 EDT by Jonathan Glaschke
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-28 15:27:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
log file (15.45 KB, text/plain)
2006-09-20 17:04 EDT, Jonathan Glaschke
no flags Details

  None (edit)
Description Jonathan Glaschke 2006-09-19 18:53:45 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv: Gecko/20060913 Fedora/ Firefox/ pango-text

Description of problem:
Nearly everytime after a created a new workspace (using switch workspace -> create new directory) and then opening the CVS Perspective, eclipse tells me that there are perblems opening the perspective.

I uploaded a screenshat to http://jogla.net/_files/shot1.png

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start eclipse
2. switch workspace
3. open cvs perspective

Actual Results:
Eclipse does not lead the perspective and throws an error instead.

Expected Results:
The CVS perspective should appear.

Additional info:
There is nothing special
Comment 1 Ben Konrath 2006-09-20 13:11:26 EDT
I get the same behaviour. Can you attach your workspace/.metadata/.log file so
that I can be sure it's the same issue. Thanks.
Comment 2 Jonathan Glaschke 2006-09-20 17:04:35 EDT
Created attachment 136782 [details]
log file
Comment 3 Ben Konrath 2006-09-28 15:27:48 EDT

*** This bug has been marked as a duplicate of 202081 ***

Note You need to log in before you can comment on or make changes to this bug.