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

There was an error checking for updates. #15417

Closed
1 task done
zhiyisun opened this issue Aug 23, 2017 · 20 comments
Closed
1 task done

There was an error checking for updates. #15417

zhiyisun opened this issue Aug 23, 2017 · 20 comments
Labels
auto-updater mac Issues that occur on macOS but not on other platforms. stale

Comments

@zhiyisun
Copy link

zhiyisun commented Aug 23, 2017

Prerequisites

Description

Hello,

When I click Atom -> Check for update, I got this error message.

"There was an error checking for updates. The command is disabled and cannot be executed. " And in Atom -> About Atom, it also shows "The command is disabled and cannot be executed." I saw some tickets said that after upgrading and relaunching atom, it shows up. But in my case, it is always show this. I have to install latest version manually.

Steps to Reproduce

  1. Atom -> Check for Update or Atom -> About Atom.

Expected behavior: [What you expect to happen]
Be able to update Atom or see message like "this is the latest version"

Actual behavior: [What actually happens]
"There was an error checking for updates. The command is disabled and cannot be executed. "

Reproduces how often: [What percentage of the time does it reproduce?]
Every time. Can't update atom at all.

Versions

atom -v
Atom : 1.19.3
Electron: 1.6.9
Chrome : 56.0.2924.87
Node : 7.4.0
apm -v
apm 1.18.4
npm 3.10.10
node 6.9.5 x64
python 2.7.10
git 2.11.0

screen shot 2017-08-23 at 15 08 20

screen shot 2017-08-23 at 15 13 40

@tomgreer
Copy link

I have the same problem running on OS X 10.12.6

@BEFH
Copy link

BEFH commented Aug 24, 2017

I, too, have this problem. MacOS 10.12.6

@zhiyisun
Copy link
Author

My friend's macbook pro doesn't have this issue. Same MacOS 10.12.6. The only difference from "apm -v" is Python version is 3. I installed Python 3. But I tried to install python 3, the issue is still there.

@zhiyisun
Copy link
Author

zhiyisun commented Sep 4, 2017

Hello rsese,

My issue is still there after I tried the solution in #15398 .

[zhisun01:~] 24m31s % apm outdated; apm update;
Package Updates Available (1)
└── vim-mode-plus 1.0.0 -> 1.3.3
Package Updates Available (1)
└── vim-mode-plus 1.0.0 -> 1.3.3

Would you like to install these updates? (yes) yes

Installing vim-mode-plus@1.3.3 to /Users/zhisun01/.atom/packages ✓

@naunga
Copy link

naunga commented Sep 6, 2017

I don't know if this is helpful or not, but this is the message I'm getting in my ShipIt_stderr.log when I try to update Atom:

2017-09-06 16:40:25.249 ShipIt[11680:16322698] Resuming installation attempt 3
2017-09-06 16:41:34.907 ShipIt[11680:16322699] Installation error: Error Domain=SQRLInstallerErrorDomain Code=-1 "Failed to copy bundle file:///Users/asalvo13/Library/Caches/com.github.atom.ShipIt/update.T0FVdja/Atom.app/ to directory file:///var/folders/9d/rf342xqx2zz5dh4y65dcq4t95q1rch/T/com.github.atom.ShipIt.MrGBl8ar/Atom.app" UserInfo={NSSourceFilePathErrorKey=/Users/asalvo13/Library/Caches/com.github.atom.ShipIt/update.T0FVdja/Atom.app/Contents/Resources/app/node_modules/babel-generator/node_modules/lodash/sum.js, NSUserStringVariant=(
    Copy
), NSDestinationFilePath=/var/folders/9d/rf342xqx2zz5dh4y65dcq4t95q1rch/T/com.github.atom.ShipIt.MrGBl8ar/Atom.app/Contents/Resources/app/node_modules/babel-generator/node_modules/lodash/sum.js, NSFilePath=/Users/asalvo13/Library/Caches/com.github.atom.ShipIt/update.T0FVdja/Atom.app/Contents/Resources/app/node_modules/babel-generator/node_modules/lodash/sum.js, NSUnderlyingError=0x7fe2da5d7070 {Error Domain=NSCocoaErrorDomain Code=4 "The file “sum.js” doesn’t exist." UserInfo={NSSourceFilePathErrorKey=/Users/asalvo13/Library/Caches/com.github.atom.ShipIt/update.T0FVdja/Atom.app/Contents/Resources/app/node_modules/babel-generator/node_modules/lodash/sum.js, NSUserStringVariant=(
    Copy
), NSDestinationFilePath=/var/folders/9d/rf342xqx2zz5dh4y65dcq4t95q1rch/T/com.github.atom.ShipIt.MrGBl8ar/Atom.app/Contents/Resources/app/node_modules/babel-generator/node_modules/lodash/sum.js, NSFilePath=/Users/asalvo13/Library/Caches/com.github.atom.ShipIt/update.T0FVdja/Atom.app/Contents/Resources/app/node_modules/babel-generator/node_modules/lodash/sum.js, NSUnderlyingError=0x7fe2df1738d0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}}, NSLocalizedDescription=Failed to copy bundle file:///Users/asalvo13/Library/Caches/com.github.atom.ShipIt/update.T0FVdja/Atom.app/ to directory file:///var/folders/9d/rf342xqx2zz5dh4y65dcq4t95q1rch/T/com.github.atom.ShipIt.MrGBl8ar/Atom.app}
2017-09-06 16:41:34.907 ShipIt[11680:16322699] ShipIt quitting

Kind of looks like it might be an issue with Lodash. ¯_(ツ)_/¯

@naunga
Copy link

naunga commented Sep 6, 2017

Hmmmk so I got this update installed and resolved the error message:

Here's what I did:

  1. Close Atom
  2. Cleared out all files and directories under ~/Library/Caches/com.github.atom.ShipIt
  3. Opened Atom.
  4. Checked for updates, then did a restart and install.
  5. Kept an eye on the ShipIt process, and after about 5 minutes Atom re-launched.

@zhiyisun
Copy link
Author

zhiyisun commented Sep 6, 2017

Thanks @naunga . But it seems this solution doesn't work for me. :-(

@zhiyisun
Copy link
Author

I tried some command option. It seems that module "auto-updater" can't be find.

screen shot 2017-09-13 at 09 13 57

@zhouyu1993
Copy link

so anybody knows ?

@onebree
Copy link

onebree commented Sep 21, 2017

I'm on macOS High Sierra. I used the AppCleaner to remove Atom v1.19.5 from my system. (The ~/.atom directory stayed in tact.) Then I installed v1.20.1, and I don't have any issues so far. I am able to manually check for updates without an error message popping up like before.

@zhouyu1993
Copy link

zhouyu1993 commented Sep 21, 2017

@onebree To use FAQ, I fix the problem.

@zhiyisun
Copy link
Author

@zhouyu1993 That FAQ doesn't fix my issue.

@rsese rsese added auto-updater mac Issues that occur on macOS but not on other platforms. labels Sep 21, 2017
@rsese
Copy link
Contributor

rsese commented Sep 21, 2017

@naunga I think you may have hit #2860?

But it doesn't sound like you're running into that issue @zhiyisun - do you see any errors related errors in Console.app?

Cross-referencing a few issues with the same "The command is disabled and cannot be executed" error:

@naunga
Copy link

naunga commented Sep 22, 2017

@rsese seems similar and I did look at that issue previously, however my login has admin rights on my laptop.

That having been said, I've run into "The command is disabled" issue again since last updating.

¯_(ツ)_/¯ computers are fun.

@rsese
Copy link
Contributor

rsese commented Sep 22, 2017

That having been said, I've run into "The command is disabled" issue again since last updating.

Ugh, do you see any related errors in Console.app?

@naunga
Copy link

naunga commented Sep 25, 2017

@rsese I do not at present. Haven't checked previously. The issue seemed to resolve itself. I wonder if it's just a matter of slow connection & large downloads?

@rsese
Copy link
Contributor

rsese commented Sep 28, 2017

I wonder if it's just a matter of slow connection & large downloads?

Not sure, though there was at least 1 other comment about timing that I remember seeing /cc #15574 (comment)

@GHuser9123
Copy link

@rsese : Hello. Started having the OP's issue yesterday (11/4/17). I first installed Atom on 10/30/17
Errors in Console.app? Yep. Including a sample below. (Note: I've subbed "[WhoIAm]" for my actual username.)

_

  • 11/5/17 7:14:03.035 PM Atom[6238]: Download completed to: file:///Users/[WhoIAm]/Library/Caches/com.github.atom.ShipIt/update.cNFThhX/atom-mac.zip
  • 11/5/17 7:14:38.063 PM ShipIt[6196]: Installation error: Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied" UserInfo={NSLocalizedDescription=Permission denied}
  • 11/5/17 7:14:38.063 PM ShipIt[6196]: ShipIt quitting
  • 11/5/17 7:17:33.687 PM ShipIt[6281]: Resuming installation attempt 3
  • 11/5/17 7:17:33.700 PM ShipIt[6281]: Couldn't abort install and restore owned bundle to previous location file:///Applications/Atom.app, error NSError { domain: NSPOSIXErrorDomain, code: 2, description: "No such file or directory" }
  • 11/5/17 7:18:14.883 PM Atom[6301]: Download completed to: file:///Users/[WhoIAm]/Library/Caches/com.github.atom.ShipIt/update.vSNcKSZ/atom-mac.zip
  • 11/5/17 7:18:47.713 PM ShipIt[6281]: Installation error: Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied" UserInfo={NSLocalizedDescription=Permission denied}
  • 11/5/17 7:18:47.729 PM ShipIt[6281]: ShipIt quitting
  • 11/5/17 7:18:47.806 PM ShipIt[6339]: Too many attempts to install, aborting update
  • 11/5/17 7:18:47.808 PM ShipIt[6339]: Error aborting installation: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" UserInfo={NSLocalizedDescription=No such file or directory}
  • 11/5/17 7:18:47.857 PM ShipIt[6339]: Application launched at file:///Applications/Atom.app
  • 11/5/17 7:18:47.857 PM ShipIt[6339]: ShipIt quitting

_

OS: El Capitan 10.11.6
Atom version(s): 1.21.1 manually updated to 1.21.2 (produces the same error-- so I've disabled the auto-update option)

Tooled around the forums and saw that there was(/is?) an issue with updates for non-admin users. However, that seemed to be from a few years ago. Usually I'm just prompted to enter the admin credentials and go on my way.

I'm a novice using this for Dr. Chuck's PY4E class. So I apologize if I'm missing something very basic here. If you need additional info, please let me know (and I'll try to perform the needed steps). Thanks.

@atom atom deleted a comment Dec 3, 2017
@stale
Copy link

stale bot commented Dec 4, 2018

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. Because the Atom team treats their issues as their backlog, stale issues are closed. If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of Atom
  2. Comment that the issue is still reproducible and include:
    • What version of Atom you reproduced the issue on
    • What OS and version you reproduced the issue on
    • What steps you followed to reproduce the issue

Issues that are labeled as triaged will not be automatically marked as stale.

@stale stale bot added the stale label Dec 4, 2018
@stale stale bot closed this as completed Dec 20, 2018
@lock
Copy link

lock bot commented Jun 18, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Jun 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-updater mac Issues that occur on macOS but not on other platforms. stale
Projects
None yet
Development

No branches or pull requests

8 participants