Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

[solved] Failed to activate the linter-gcc package #123

Closed
Dynamic-Gravity opened this issue Apr 14, 2017 · 16 comments
Closed

[solved] Failed to activate the linter-gcc package #123

Dynamic-Gravity opened this issue Apr 14, 2017 · 16 comments

Comments

@Dynamic-Gravity
Copy link

Dynamic-Gravity commented Apr 14, 2017

The error I received was:

Arguments to CompositeDisposable.add must have a .dispose() method

My GCC version:

[luke@Venus 310-intermediate]$ gcc --version
gcc (GCC) 6.3.1 20170306
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

What I tried:

[luke@Venus 310-intermediate]$ apm uninstall linter
Uninstalling linter ✓
(node:13228) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[luke@Venus 310-intermediate]$ apm install linter
(node:13234) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
Installing linter to /home/luke/.atom/packages ✓
[luke@Venus 310-intermediate]$ apm uninstall linter-gcc
Uninstalling linter-gcc ✓
(node:13583) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[luke@Venus 310-intermediate]$ apm install linter-gcc
(node:13589) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
Installing linter-gcc to /home/luke/.atom/packages ✓

Here is the stack trace from the error.

TypeError: Arguments to CompositeDisposable.add must have a .dispose() method
at assertDisposable (/usr/lib/atom/node_modules/event-kit/lib/composite-disposable.js:74:13)
at CompositeDisposable.module.exports.CompositeDisposable.add (/usr/lib/atom/node_modules/event-kit/lib/composite-disposable.js:43:11)
at Object.consumeLinter (/home/luke/.atom/packages/linter-gcc/lib/main.js:211:10)
at Provider.module.exports.Provider.provide (/usr/lib/atom/node_modules/service-hub/lib/provider.js:34:52)
at ServiceHub.module.exports.ServiceHub.consume (/usr/lib/atom/node_modules/service-hub/lib/service-hub.js:50:18)
at Package.module.exports.Package.activateServices (/usr/lib/atom/src/package.js:404:75)
at Package.module.exports.Package.activateNow (/usr/lib/atom/src/package.js:221:16)
at /usr/lib/atom/src/package.js:190:32
at Package.module.exports.Package.measure (/usr/lib/atom/src/package.js:96:15)
at /usr/lib/atom/src/package.js:183:26
at Package.module.exports.Package.activate (/usr/lib/atom/src/package.js:180:34)
at PackageManager.module.exports.PackageManager.activatePackage (/usr/lib/atom/src/package-manager.js:542:34)
at /usr/lib/atom/src/package-manager.js:523:29
at Config.module.exports.Config.transactAsync (/usr/lib/atom/src/config.js:337:18)
at PackageManager.module.exports.PackageManager.activatePackages (/usr/lib/atom/src/package-manager.js:518:19)
at PackageManager.module.exports.PackageManager.activate (/usr/lib/atom/src/package-manager.js:500:46)
at /usr/lib/atom/src/atom-environment.js:826:28

What would be the next step if uninstalling/reinstalling the linter and linter-gcc packages doesn't work?

EDIT: What it looks like with other people's comments, the lasted update broke something.

@Dynamic-Gravity
Copy link
Author

@mpcmarques Did you just do an update too?

@Superdanby
Copy link

+1
after the update.

@MacWyznawca
Copy link

+1
I too :-(
macOS 10.12.5 Beta (16F54b)

@softsmyth
Copy link

softsmyth commented Apr 14, 2017

+1
fresh install of PlatformIO on Debian 8.7.1

@corbin-r
Copy link

Get the same stack trace as @Dynamic-Gravity
Running macOS Sierra 10.12.4
Attempted uninstall and reinstall of both linter and linter-gcc through APM but didn't work.

@arthurphilippe
Copy link

+1
After the update all the same
On arch

@Dynamic-Gravity
Copy link
Author

@arthur29498 I'm on arch as well.

@phrockell
Copy link

Same on Linux Mint 18, with a cleanly installed Atom IDE.

@Arcanemagus
Copy link
Member

Can any of you point to a recent change that would have triggered this?

Did the latest linter update 4 hours ago break this? You can force install the older version to check with apm install linter@2.1.2.

@Dynamic-Gravity
Copy link
Author

@Arcanemagus, yes I believe that is what broke this. As I was using Atom this morning, then noticed an update with that package, after which this error occurred.

@steelbrain
Copy link

Sorry everyone, you can expect a bugfix release in a few minutes, we (base linter team) messed up 🙇 steelbrain/linter#1434

@Dynamic-Gravity
Copy link
Author

@steelbrain thanks for the update!

@steelbrain
Copy link

steelbrain commented Apr 14, 2017

Sorry again for the trouble everyone, Linter v2.1.4 is out with the fix

@Dynamic-Gravity
Copy link
Author

@steelbrain thank you, linter-gcc is working again.

@Dynamic-Gravity Dynamic-Gravity changed the title Failed to activate the linter-gcc package [solved] Failed to activate the linter-gcc package Apr 14, 2017
@Dynamic-Gravity Dynamic-Gravity mentioned this issue Apr 14, 2017
4 tasks
@corbin-r
Copy link

corbin-r commented Apr 14, 2017

Awesome! Thanks @steelbrain and co. Will re-download now.

EDIT Can confirm it now works on macOS Sierra 10.12.4

@softsmyth
Copy link

looks good now... thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants