Failed to activate the language-csharp package

[anigan]

[Enter steps to reproduce:]

1. ...
2. ...

Atom: 1.30.0 x64
Electron: 2.0.5
OS: Microsoft Windows 10 Enterprise
Thrown From: language-csharp package 1.0.4

Stack Trace

Failed to activate the language-csharp package

At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at Function.module.exports.Emitter.simpleDispatch (~/AppData/Local/atom/app-1.30.0/resources/app/node_modules/event-kit/lib/emitter.js:27:20)
    at Emitter.module.exports.Emitter.emit (~/AppData/Local/atom/app-1.30.0/resources/app/node_modules/event-kit/lib/emitter.js:156:34)
    at GrammarRegistry.module.exports.GrammarRegistry.addGrammar (~/AppData/Local/atom/app-1.30.0/resources/app/node_modules/first-mate/lib/grammar-registry.js:80:26)
    at Grammar.module.exports.Grammar.activate (~/AppData/Local/atom/app-1.30.0/resources/app/node_modules/first-mate/lib/grammar.js:259:54)
    at Package.activateResources (~/AppData/Local/atom/app-1.30.0/resources/app/src/package.js:319:23)
    at measure (~/AppData/Local/atom/app-1.30.0/resources/app/src/package.js:202:24)
    at Package.measure (~/AppData/Local/atom/app-1.30.0/resources/app/src/package.js:88:25)
    at activationPromise.Promise (~/AppData/Local/atom/app-1.30.0/resources/app/src/package.js:200:20)
    at new Promise (<anonymous>)
    at Package.activate (~/AppData/Local/atom/app-1.30.0/resources/app/src/package.js:198:38)
    at PackageManager.activatePackage (~/AppData/Local/atom/app-1.30.0/resources/app/src/package-manager.js:695:42)
    at packagesToEnable.forEach.name (~/AppData/Local/atom/app-1.30.0/resources/app/src/package-manager.js:440:51)
    at Array.forEach (<anonymous>)
    at disabledPackagesSubscription.config.onDidChange (~/AppData/Local/atom/app-1.30.0/resources/app/src/package-manager.js:440:30)
    at emitter.on (~/AppData/Local/atom/app-1.30.0/resources/app/src/config.js:1067:22)
    at Function.module.exports.Emitter.simpleDispatch (~/AppData/Local/atom/app-1.30.0/resources/app/node_modules/event-kit/lib/emitter.js:27:20)
    at Emitter.module.exports.Emitter.emit (~/AppData/Local/atom/app-1.30.0/resources/app/node_modules/event-kit/lib/emitter.js:156:34)
    at Config.emitChangeEvent (~/AppData/Local/atom/app-1.30.0/resources/app/src/config.js:1226:62)
    at Config.setRawValue (~/AppData/Local/atom/app-1.30.0/resources/app/src/config.js:1052:23)
    at Config.set (~/AppData/Local/atom/app-1.30.0/resources/app/src/config.js:715:18)
    at Config.removeAtKeyPath (~/AppData/Local/atom/app-1.30.0/resources/app/src/config.js:905:16)
    at Package.enable (~/AppData/Local/atom/app-1.30.0/resources/app/src/package.js:75:30)
    at PackageManager.enablePackage (~/AppData/Local/atom/app-1.30.0/resources/app/src/package-manager.js:246:18)
    at HTMLButtonElement.enablementButtonClickHandler (~/AppData/Local/atom/app-1.30.0/resources/app/node_modules/settings-view/lib/package-card.js:362:31)

Commands

 26x -2:45.9.0 core:backspace (input.hidden-input)
     -2:32.7.0 autocomplete-plus:confirm (input.hidden-input)
     -2:32.6.0 snippets:expand (atom-text-editor.editor.is-focused.autocomplete-active)
  2x -1:50 tree-view:remove (span.name.icon.icon-file-text)
     -1:31.4.0 tree-view:add-file (span.name.icon.icon-file-directory)
  3x -1:23.9.0 core:backspace (input.hidden-input)
  2x -1:23.1.0 core:confirm (input.hidden-input)

Non-Core Packages

autocomplete-bash-builtins 0.3.5 
autocomplete-python 1.10.10 
busy-signal 1.4.3 
intentions 1.1.5 
language-powershell 4.0.1 
linter 2.2.0 
linter-ui-default 1.7.1 
omnisharp-atom 0.31.2 

[rsese]

Thanks for the report! Based on the stacktrace, I think you might be hitting this issue:

OmniSharp/omnisharp-atom#1020

So it appears that this is being caused by https://github.com/OmniSharp/omnisharp-atom and not Atom itself. It may be that there is still a bug in Atom. If so, we'll need the maintainer of the package that is causing the problem to help track that down. You should file this issue on their repository so they can either fix the problem or tell us where the problem is coming from. The Atom FAQ has information on how to contact the maintainers of any Atom community package or theme.