370093 – Save commands are disabled on changed, "dirty" document.

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 370093 - Save commands are disabled on changed, "dirty" document.

Summary: Save commands are disabled on changed, "dirty" document.

Status:	CLOSED DUPLICATE of bug 361136

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	IDE (show other bugs)
Version:	3.7.1
Hardware:	PC Linux

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-01-30 02:53 EST by Lukas Glowania
Modified:	2012-01-30 05:13 EST (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Lukas Glowania

2012-01-30 02:53:22 EST

Build Identifier: 20110916-0149

Sometimes when i switch to an editor-tab in which an unsaved, dirty document resides "Save", "Save As..." and "Save All" are disabled. 
Ctrl+S also does not work.
The document is definitely dirty and the "*" occurs in the tab's title.
When i switch to a different tab and back, the Save commands are enabled again.
I have used Eclipse for a long time and the Indigo version is the first where i encounter this behaviour.

Reproducible: Sometimes

Steps to Reproduce:
I don't know how to reproduce. However it occurs approximately 1 time per hour of regular work.

Comment 1 Deepak Azad

2012-01-30 03:02:58 EST

The symptoms look same as bug 361136.

Which Linux flavor are you using - Ubuntu?

Comment 2 Lukas Glowania

2012-01-30 03:44:31 EST

(In reply to comment #1)
> The symptoms look same as bug 361136.
> 
> Which Linux flavor are you using - Ubuntu?

I'm on Linx Mint 12. I haven't noticed the correlation to quick fix as in bug 361136, but probably it's the same bug.

Comment 3 Lukas Glowania

2012-01-30 05:13:15 EST


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