Bug 293910 - [WorkbenchLauncher] eclipse show stop-error at startup when workspace is locked
Summary: [WorkbenchLauncher] eclipse show stop-error at startup when workspace is locked
Status: CLOSED DUPLICATE of bug 80734
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Prakash Rangaraj CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-02 05:37 EST by Vladimir Missing name CLA
Modified: 2013-11-18 11:50 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Missing name CLA 2009-11-02 05:37:50 EST
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.1.4) Gecko/20091028 Ubuntu/9.10 (karmic) Firefox/3.5.4
Build Identifier: 20090920-1017

When running eclipse after unproper shutdown I see
"Workspace in use or cannot be created, choose a different one."
It's seems confusing.
I think message should be something like:
"Warning! Current workspace is locked. Make sure there is no other copies of eclipse running. Proceed (remove lock and continue)? Yes/No/Create new workspace".

Reproducible: Always

Steps to Reproduce:
1. run eclipse, create some project at workspace
2. poweroff machine :)
3. run eclipse again
Comment 1 Ralf Ebert CLA 2009-11-02 06:54:33 EST
In general you're right, but I'm not sure if it should be easy to remove the lock. If you remove the lock by mistake while another instance uses the workspace, this might cause severe corruption of the workspace files.
Comment 2 Vladimir Missing name CLA 2009-11-02 07:08:26 EST
(In reply to comment #1)
> In general you're right, but I'm not sure if it should be easy to remove the
> lock. If you remove the lock by mistake while another instance uses the
> workspace, this might cause severe corruption of the workspace files.

I did remove it just typing:
$ rm ~/workspace/.metadata/.lock

In general user has to be asked "If there is no other instance, lock will be removed. Agree [yes/no]?".

At least user need information what to do: check other instances/remove lock by hands(?) if no instances or something else.

As for me, after notice about unable to use workspace I have no choice to continue work.
Comment 3 Boris Bokowski CLA 2009-11-26 16:32:48 EST
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
Comment 4 Martin Oberhuber CLA 2013-11-18 11:48:45 EST
This looks like a duplicate of https://bugs.eclipse.org/bugs/show_bug.cgi?id=80734
Comment 5 Paul Webster CLA 2013-11-18 11:50:39 EST

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