Pydev workspaces become corrupted after loading them without Pydev installed

Bug #1075747 reported by Alberto Salvia Novella
24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eclipse
New
Undecided
rashaad lane
eclipse (Ubuntu)
Fix Released
Critical
rashaad lane

Bug Description

STEPS FOR REPRODUCING
*********************

Warning: This procedure will remove all your Eclipse's add-ons.

1. Switch to a new and never used workspace by using the provider functionality at the “File/Switch workspace/Other...” menu.

2. Install Pydev from http://pydev.org/updates by using the provided functionality at the “Help/Install new software” menu.

3. Create a new Pydev project.

4. Close Eclipse.

5. Delete the folder named “.eclipse” in your personal folder. If you don't see it, you can show it by going to the “Edit/Preferences/Views/Default view” menu in the file explorer, and by marking the “Show the hidden and backup folders” option.

6. Restart Eclipse and choose the workspace you created in the beginning.

EXPECTED BEHAVIOUR
******************

The workspace to initiate.

REAL BEHAVIOUR
**************

Eclipse hangs and the workspace becomes corrupted, and can never be opened again.

WORKAROUNDS
***********

>> For starting Eclipse at first run preventing your Pydev workspace to become corrupted:

1. Start Eclipse by choosing a workspace never used.

2. Install Pydev.

3. Close Eclipse.

4. Delete the workspace you have just created.

>> For recovering a broken workspace:

1. Close Eclipse.

2. Rename the workspace to [workspace-name].back

3. Create a folder called [workspace-name]

4. Open Eclipse and choose [workspace-name] as workspace.

5. Import [workspace-name].back projects into the current workspace by right-clicking on the Project Explorer section and choosing “Import...”. They should be imported as filesystem.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: eclipse-platform 3.8.0~rc4-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
Date: Tue Nov 6 22:22:58 2012
InstallationDate: Installed on 2012-11-03 (3 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
SourcePackage: eclipse
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
description: updated
summary: - Unable to load Ubuntu One synced workspaces
+ Pydev workspaces become corupted after loading them without Pydev
+ installed
description: updated
description: updated
Changed in eclipse (Ubuntu):
importance: Undecided → Critical
Rajiv Shah (rajivshah3)
Changed in eclipse (Ubuntu):
status: New → Incomplete
status: Incomplete → Confirmed
Changed in eclipse (Ubuntu):
status: Confirmed → Triaged
Anders (eddiedog988)
Changed in eclipse (Ubuntu):
status: Triaged → Confirmed
Changed in eclipse (Ubuntu):
status: Confirmed → Triaged
summary: - Pydev workspaces become corupted after loading them without Pydev
+ Pydev workspaces become corrupted after loading them without Pydev
installed
Revision history for this message
elatllat (elatllat) wrote :

DistroRelease: Ubuntu 16.04
Package: eclipse-platform 3.x

Updating the package to 4.7.2 and getting the last 6? years of work might solve this and related bugs.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681726

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Nobody cares.

summary: - Pydev workspaces become corrupted after loading them without Pydev
- installed
+ Buy Xanax Online:: Facts about Anxiety Attacks
description: updated
description: updated
Matthias Klose (doko)
summary: - Buy Xanax Online:: Facts about Anxiety Attacks
+ Pydev workspaces become corrupted after loading them without Pydev
+ installed
description: updated
Changed in eclipse-eclipsers:
assignee: nobody → rashaad lane (zillablack)
Changed in eclipse (Ubuntu):
assignee: nobody → rashaad lane (zillablack)
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.