How to upgrade Atom from webupd8team/atom to the offical packagecloud.io/AtomEditor/atom
Not until very recently you couldn't apt install atom unless you use an unoffical source webupd8team/atom. Now Atom officially supports apt install by packagecloud.io/AtomEditor/atom. But upgrading 1.26.1-1~webupd8~0 to 1.33.0 using the official source resulted in an Atom that can't open any windows on my machine. e.g. No Ctrl + Comma, no Welcome Guide, no About Atom.
After I re-installed the webupd8team version everything went back to normal. Then I tried everything. Before doing the following I sudo apt purge atom first.
- Install from software center.
- Install from
.deb
- Install 1.32.2 from
packagecloud.io/AtomEditor/atom
- Install 1.26.1 from
packagecloud.io/AtomEditor/atom
4 worked!! Also the official 1.33.0 can be installed in my virtual machine which is running 18.04 and had a 1.26.1 webupd8team version installed before.
My best guess is it could be something in my system that is incompatible with 1.26+ (1.29.0 also presents the same symptom), and it's not on my virtual machine. What it could be?
atom
add a comment |
Not until very recently you couldn't apt install atom unless you use an unoffical source webupd8team/atom. Now Atom officially supports apt install by packagecloud.io/AtomEditor/atom. But upgrading 1.26.1-1~webupd8~0 to 1.33.0 using the official source resulted in an Atom that can't open any windows on my machine. e.g. No Ctrl + Comma, no Welcome Guide, no About Atom.
After I re-installed the webupd8team version everything went back to normal. Then I tried everything. Before doing the following I sudo apt purge atom first.
- Install from software center.
- Install from
.deb
- Install 1.32.2 from
packagecloud.io/AtomEditor/atom
- Install 1.26.1 from
packagecloud.io/AtomEditor/atom
4 worked!! Also the official 1.33.0 can be installed in my virtual machine which is running 18.04 and had a 1.26.1 webupd8team version installed before.
My best guess is it could be something in my system that is incompatible with 1.26+ (1.29.0 also presents the same symptom), and it's not on my virtual machine. What it could be?
atom
1
I tried that and it didn't work. I updated my question to record the progress on this problem.
– Xiaohong Deng
Dec 14 '18 at 6:38
add a comment |
Not until very recently you couldn't apt install atom unless you use an unoffical source webupd8team/atom. Now Atom officially supports apt install by packagecloud.io/AtomEditor/atom. But upgrading 1.26.1-1~webupd8~0 to 1.33.0 using the official source resulted in an Atom that can't open any windows on my machine. e.g. No Ctrl + Comma, no Welcome Guide, no About Atom.
After I re-installed the webupd8team version everything went back to normal. Then I tried everything. Before doing the following I sudo apt purge atom first.
- Install from software center.
- Install from
.deb
- Install 1.32.2 from
packagecloud.io/AtomEditor/atom
- Install 1.26.1 from
packagecloud.io/AtomEditor/atom
4 worked!! Also the official 1.33.0 can be installed in my virtual machine which is running 18.04 and had a 1.26.1 webupd8team version installed before.
My best guess is it could be something in my system that is incompatible with 1.26+ (1.29.0 also presents the same symptom), and it's not on my virtual machine. What it could be?
atom
Not until very recently you couldn't apt install atom unless you use an unoffical source webupd8team/atom. Now Atom officially supports apt install by packagecloud.io/AtomEditor/atom. But upgrading 1.26.1-1~webupd8~0 to 1.33.0 using the official source resulted in an Atom that can't open any windows on my machine. e.g. No Ctrl + Comma, no Welcome Guide, no About Atom.
After I re-installed the webupd8team version everything went back to normal. Then I tried everything. Before doing the following I sudo apt purge atom first.
- Install from software center.
- Install from
.deb
- Install 1.32.2 from
packagecloud.io/AtomEditor/atom
- Install 1.26.1 from
packagecloud.io/AtomEditor/atom
4 worked!! Also the official 1.33.0 can be installed in my virtual machine which is running 18.04 and had a 1.26.1 webupd8team version installed before.
My best guess is it could be something in my system that is incompatible with 1.26+ (1.29.0 also presents the same symptom), and it's not on my virtual machine. What it could be?
atom
atom
edited Dec 14 '18 at 6:45
Xiaohong Deng
asked Dec 14 '18 at 2:42
Xiaohong DengXiaohong Deng
214
214
1
I tried that and it didn't work. I updated my question to record the progress on this problem.
– Xiaohong Deng
Dec 14 '18 at 6:38
add a comment |
1
I tried that and it didn't work. I updated my question to record the progress on this problem.
– Xiaohong Deng
Dec 14 '18 at 6:38
1
1
I tried that and it didn't work. I updated my question to record the progress on this problem.
– Xiaohong Deng
Dec 14 '18 at 6:38
I tried that and it didn't work. I updated my question to record the progress on this problem.
– Xiaohong Deng
Dec 14 '18 at 6:38
add a comment |
1 Answer
1
active
oldest
votes
The answer is atom installed from sources other than webupd8team/atom does not have permission to access ~/.atom/compile-cache. sudo apt purge atom doesn't delete that folder. So atom gets denied when trying to access files in that folder.
By open the web console using Shift + Ctrl + i you can see what error is occurring behind the scene.
The solution is easy. First, delete ~/.atom/compile-cache. Then purge atom, fresh install atom from the source of your choice. Remember to remove the outdated ppa afterwards.
More info please refer to the thread Problem with starting up atom
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100771%2fhow-to-upgrade-atom-from-webupd8team-atom-to-the-offical-packagecloud-io-atomedi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The answer is atom installed from sources other than webupd8team/atom does not have permission to access ~/.atom/compile-cache. sudo apt purge atom doesn't delete that folder. So atom gets denied when trying to access files in that folder.
By open the web console using Shift + Ctrl + i you can see what error is occurring behind the scene.
The solution is easy. First, delete ~/.atom/compile-cache. Then purge atom, fresh install atom from the source of your choice. Remember to remove the outdated ppa afterwards.
More info please refer to the thread Problem with starting up atom
add a comment |
The answer is atom installed from sources other than webupd8team/atom does not have permission to access ~/.atom/compile-cache. sudo apt purge atom doesn't delete that folder. So atom gets denied when trying to access files in that folder.
By open the web console using Shift + Ctrl + i you can see what error is occurring behind the scene.
The solution is easy. First, delete ~/.atom/compile-cache. Then purge atom, fresh install atom from the source of your choice. Remember to remove the outdated ppa afterwards.
More info please refer to the thread Problem with starting up atom
add a comment |
The answer is atom installed from sources other than webupd8team/atom does not have permission to access ~/.atom/compile-cache. sudo apt purge atom doesn't delete that folder. So atom gets denied when trying to access files in that folder.
By open the web console using Shift + Ctrl + i you can see what error is occurring behind the scene.
The solution is easy. First, delete ~/.atom/compile-cache. Then purge atom, fresh install atom from the source of your choice. Remember to remove the outdated ppa afterwards.
More info please refer to the thread Problem with starting up atom
The answer is atom installed from sources other than webupd8team/atom does not have permission to access ~/.atom/compile-cache. sudo apt purge atom doesn't delete that folder. So atom gets denied when trying to access files in that folder.
By open the web console using Shift + Ctrl + i you can see what error is occurring behind the scene.
The solution is easy. First, delete ~/.atom/compile-cache. Then purge atom, fresh install atom from the source of your choice. Remember to remove the outdated ppa afterwards.
More info please refer to the thread Problem with starting up atom
answered Jan 29 at 18:16
Xiaohong DengXiaohong Deng
214
214
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100771%2fhow-to-upgrade-atom-from-webupd8team-atom-to-the-offical-packagecloud-io-atomedi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I tried that and it didn't work. I updated my question to record the progress on this problem.
– Xiaohong Deng
Dec 14 '18 at 6:38