Paint text editor's cursor not working on Linux

[Hikari9]

The cursor color and even the line number color don't seem to reflect changes made to the primary/accent colors in the settings, at least in my Ubuntu 16.04 LTS. The "Paint text editor's cursor" is ticked, but the cursor is always Teal for some reason, even after I restarted Atom. I think this also applies to the other Linux distros, but please confirm.

Reproduction Steps:

1. Go to Atom Material UI Settings
2. Change Predefined colors to "Pink"
3. Check "Paint text editor's cursor"

Expected behavior:

Cursor color (and color of line number) should become Pink.

Observed behavior:

Cursor color (and color of line number) remains Teal.

Screenshots

Atom version: 1.12.6 OS and version: Ubuntu 16.04.2 LTS (xenial) 4.4.0-67-generic x86_64 GNU/Linux

Installed packages:

``` Built-in Atom Packages (89) ├── atom-dark-syntax@0.27.0 ├── atom-dark-ui@0.52.0 ├── atom-light-syntax@0.28.0 ├── atom-light-ui@0.45.0 ├── base16-tomorrow-dark-theme@1.3.0 ├── base16-tomorrow-light-theme@1.3.0 ├── one-dark-ui@1.6.2 ├── one-light-ui@1.6.2 ├── one-dark-syntax@1.5.0 ├── one-light-syntax@1.5.0 ├── solarized-dark-syntax@1.0.5 ├── solarized-light-syntax@1.0.5 ├── about@1.7.0 ├── archive-view@0.62.0 ├── autocomplete-atom-api@0.10.0 ├── autocomplete-css@0.13.1 ├── autocomplete-html@0.7.2 ├── autocomplete-plus@2.31.4 ├── autocomplete-snippets@1.11.0 ├── autoflow@0.27.0 ├── autosave@0.23.1 ├── background-tips@0.26.1 ├── bookmarks@0.42.0 ├── bracket-matcher@0.82.2 ├── command-palette@0.39.0 ├── deprecation-cop@0.54.1 ├── dev-live-reload@0.47.0 ├── encoding-selector@0.22.0 ├── exception-reporting@0.40.0 ├── find-and-replace@0.202.2 ├── fuzzy-finder@1.4.0 ├── git-diff@1.1.0 ├── go-to-line@0.31.0 ├── grammar-selector@0.48.2 ├── image-view@0.60.0 ├── incompatible-packages@0.26.1 ├── keybinding-resolver@0.35.0 ├── line-ending-selector@0.5.0 ├── link@0.31.2 ├── markdown-preview@0.158.8 ├── metrics@1.1.2 ├── notifications@0.65.1 ├── open-on-github@1.2.1 ├── package-generator@1.0.1 ├── settings-view@0.243.1 ├── snippets@1.0.4 ├── spell-check@0.68.4 ├── status-bar@1.4.1 ├── styleguide@0.47.2 ├── symbols-view@0.113.1 ├── tabs@0.103.0 ├── timecop@0.33.2 ├── tree-view@0.210.0 ├── update-package-dependencies@0.10.0 ├── welcome@0.35.1 ├── whitespace@0.35.0 ├── wrap-guide@0.38.2 ├── language-c@0.54.0 ├── language-clojure@0.22.1 ├── language-coffee-script@0.48.0 ├── language-csharp@0.13.0 ├── language-css@0.40.1 ├── language-gfm@0.88.0 ├── language-git@0.15.0 ├── language-go@0.43.0 ├── language-html@0.47.1 ├── language-hyperlink@0.16.1 ├── language-java@0.24.0 ├── language-javascript@0.122.0 ├── language-json@0.18.3 ├── language-less@0.29.6 ├── language-make@0.22.2 ├── language-mustache@0.13.0 ├── language-objective-c@0.15.1 ├── language-perl@0.37.0 ├── language-php@0.37.3 ├── language-property-list@0.8.0 ├── language-python@0.45.1 ├── language-ruby@0.70.2 ├── language-ruby-on-rails@0.25.1 ├── language-sass@0.57.0 ├── language-shellscript@0.23.0 ├── language-source@0.9.0 ├── language-sql@0.25.0 ├── language-text@0.7.1 ├── language-todo@0.29.1 ├── language-toml@0.18.1 ├── language-xml@0.34.12 └── language-yaml@0.27.1 Community Packages (25) /home/rico/.atom/packages ├── angularjs@0.4.0 ├── atom-autocomplete-php@0.22.0 ├── atom-live-server@2.1.2 ├── atom-material-syntax@0.4.6 ├── atom-material-syntax-dark@0.2.6 ├── atom-material-syntax-light@0.4.6 ├── atom-material-ui@1.3.9 ├── autoclose-html@0.23.0 ├── autocomplete-ionic-framework@0.2.2 ├── autocomplete-java@1.2.5 ├── autocomplete-json@5.3.0 ├── autocomplete-modules@1.6.7 ├── autocomplete-python@1.8.57 ├── autocomplete-xml@0.9.4 ├── language-cpp14@0.6.2 ├── language-racket@0.4.0 ├── linter@1.11.18 ├── linter-eslint@8.1.2 ├── linter-gcc@0.7.1 ├── linter-javac@1.9.4 ├── linter-jscs@4.1.2 ├── linter-sass-lint@1.7.4 ├── node-debugger@1.10.1 ├── rest-client@1.3.1 └── save-autorun@0.3.3 └── (empty) ```

[silvestreh]

That's odd, it's working on my end. Atom 1.13 introduced some breaking changes with syntax themes that could be producing this behavior. Could you upgrade your Atom editor?

[Hikari9]

It works now. Just needed to update Atom like you said. Thanks, @silvestreh.