Bug 549103 - Ctrl + A and Ctrl + S not working with Build id: I20190708-1800
Summary: Ctrl + A and Ctrl + S not working with Build id: I20190708-1800
Status: CLOSED DUPLICATE of bug 546932
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows 7
: P3 blocker (vote)
Target Milestone: 4.13 M1   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2019-07-09 09:49 EDT by Niraj Modi CLA
Modified: 2019-07-25 06:20 EDT (History)
7 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 Niraj Modi CLA 2019-07-09 09:49:17 EDT 
Steps to reproduce:
1. Launch Eclipse Build id: I20190708-1800
2. Modify any Java file
3. On pressing Ctrl+S and Ctrl+A nothing happens.

Just restarted Eclipse, but same result.
Comment 1 Niraj Modi CLA 2019-07-09 09:57:27 EDT 
Restarted my machine and problem persists.
Comment 2 Andrey Loskutov CLA 2019-07-09 09:58:54 EDT 
Any errors in the log? I can't see this on RHEL 7.5.
Comment 3 Alexander Kurtakov CLA 2019-07-09 09:59:17 EDT 
Works for me on Fedora 30 too.
Comment 4 Dani Megert CLA 2019-07-09 10:11:25 EDT 
Works for me using eclipse-SDK-I20190709-0610-win32-x86_64:

1. Start new workspace
2. Paste "class Works {}"
3. Ctrl+A works
4. Make a change
5. Ctrl+S works
Comment 5 Niraj Modi CLA 2019-07-09 10:13:37 EDT 
(In reply to Dani Megert from comment #4)
> Works for me using eclipse-SDK-I20190709-0610-win32-x86_64:
> 
> 1. Start new workspace
> 2. Paste "class Works {}"
> 3. Ctrl+A works
> 4. Make a change
> 5. Ctrl+S works

Just checked. Looks like a problem with my workspace, with a fresh workspace it's working fine for me.
Comment 6 Niraj Modi CLA 2019-07-25 06:20:36 EDT 
Suggestion in below comment worked for me, removed the workbench.xmi:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=546932#c38

Marking this bug as duplicate of bug 546932.

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