Problems occurred restoring workbench.

Christoph, what were you doing when this happened?

Sometimes if you open a workspace after installing something different in eclipse or open it with a new eclipse installation, it's just telling you that the view you had before isn't there any more. It's not necessarily a bug.
Was everything ok after you either restored the perspective, or it did that itself?

P.S. When you tell us the version, if you can also give the "v2010mmddxxxx" number at the end, that will help us know exactly which one you have. Don't know if if makes any difference in this case, but it could be helpful in some cases.

Beth,

I thought that error was reproducible - but I just opened the workspace without hitting this error.....Ok, I had to retry a couple of times (open workspace - close - open - run an X10 program that got an error - close - open - boom !! - clear log - close - open -boom again !!). Means, it is isn't reproducible at every opening of a workspace. I am not missing any particular view in any perspective after the error is flagged.

As for the X10DT version, is this what you are looking for ?
x10.common (2.0.1.v201002031506) "X10 Common components" [Resolved]
x10.compiler (2.0.1.v201002031506) "X10 compiler" [Resolved]
x10.constraints (2.0.1.v201002031506) "X10 Constraints" [Resolved]
x10.dist.host (2.0.1.v201002031506) "Host (central) plugin for x10 platform-specific fragments" [Starting]
x10.dist.linux.x86.fragment (2.0.1.v201002031506) "x10 dist for Linux X86" [Resolved]
x10.effects (2.0.1.v201002031506) "Effects" [Resolved]
x10.runtime (2.0.1.v201002031506) "X10 runtime" [Starting]

Hope that helps !

Christoph

Bulk assign all unscheduled issues with priority major or less to 2.1.0 target.

bulk move of all unresolved issues from 2.1.1 to 2.1.2

defer all non-critical 2.1.2 issues to 2.2.

bulk defer minor/trivial issues to 2.2.1.

bulk defer minor issues to 2.2.2

bulk defer of issues to 2.2.3.

bulk defer of 2.3.0 open issues to 2.3.1.

bulk defer to 2.3.2