Summary: | [ErrorHandling] [WorkbenchLauncher] Give a hint how to recover from "Workspace cannot be locked" | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Ralf Hauser <hauser> | ||||||
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Susan McCourt <susan> | ||||||
Severity: | enhancement | ||||||||
Priority: | P5 | CC: | krzysztof.daniel, mober.at+eclipse | ||||||
Version: | 3.0.1 | Keywords: | helpwanted | ||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Ralf Hauser
2004-10-20 00:11:29 EDT
Created attachment 15292 [details]
workSpaceCannotBeLocked.png
please provide a text how to recover from this or at least a link to some
explanatory text?
While not visible on the screen, with alt-ctrl-del, I noticed that another
instance of eclipse was still running and once I killed it, I could continue to
work.
Do you have a suggestion? Sometimes giving more specific information about why the problem has occured causes the user to assume a certain scenario, when in actual fact we don't know precisely why this is occuring and may be misleading. Reassigning bugs to reflect changes in ownership. ping. I think this is no longer issue because since eclipse 3.3 (I think) there is no separate process for locking workspace... I am not sure what was the change exactly. Agreed. Marking as WONTFIX. unfortunately, still happens with v3.3 Created attachment 110737 [details]
workspaceLocked_v3.3_080823.png
slightly different text, killing the hanging eclipse process didn't help this time
Ralf, does this issue still happens on 3.4 or 3.5? This looks like a duplicate of https://bugs.eclipse.org/bugs/show_bug.cgi?id=80734 *** This bug has been marked as a duplicate of bug 80734 *** |