Vscode-icons: no longer works under ubuntu 16.4

[NikosEfthias]

today when i open noticed that icons are not working anymore the /usr/share/code forlder is owned by me and the exnsion is enabled but its no working

[robertohuertasm]

Can anyone confirm this? I'm on holidays and have limited access to the internet and linux vms 😞
I'll try to check it out asap.

[ekmlarbi]

Yes its just as @NikosEfthias said. In my case I had it running in vscode 1.0.0 on 16.04. After upgrading to vscode 1.3.1 today it stopped working. My ownership of the folder /usr/share/code is intact and I have enabled the extension.

[robertohuertasm]

Which version of the extension are you running?

[robertohuertasm]

@NikosEfthias can you tell me if it stopped working with the latest version of the extension? Can you both open the dev tools in your vscode and let me know what you see in there?

[ekmlarbi]

@robertohuertasm, Here is what I am using:
vscode-icons [1.5.2],
vscode [1.3.1]
Let me know what i should be looking for in vscode devtool.

[robertohuertasm]

I've tested it with Ubuntu 15.04 and it's working perfectly. Unfortunately, I have no full internet access and can't access to 16.04. @ekmlarbi, take a look into the console and look for error messages.

[robertohuertasm]

Have you tried reinstalling VS Code?

[frkn-aydn]

Same here :( i am using ubuntu 16.04

[robertohuertasm]

@birz4man can you look into the dev tools and look for some error messages?

[NikosEfthias]

there is no error on the developer tools

[NikosEfthias]

1.5.2 btw my vscode-icons version is and 1.3.1 vscode version

[robertohuertasm]

Any of you have tried reinstalling vscode?

[NikosEfthias]

now trying give me a sec :)

[frkn-aydn]

OK :) nikos help me now. Thx nikos i fixed :)

[robertohuertasm]

@birz4man what did you do?

[NikosEfthias]

he just didnt own the /usr/share/code folder @robertohuertasm

[robertohuertasm]

ok, but I guess you're still having the issue, aren't you? Or did reinstalling do the trick?

[NikosEfthias]

i just reinstalled and still not working this happened after the latest update only before it was working @robertohuertasm

[robertohuertasm]

For what we know @birz4man has your same settings. @birz4man can you confirm this?

[frkn-aydn]

yes @robertohuertasm

[robertohuertasm]

@NikosEfthias The most strange thing is you not seeing some errors in the console. A lack of permissions will trigger a vscode warning and any other thing will raise an error... or it should have to raise an error... clearly there's something that we're missing. Reinstalling should leave your original files cleaned... have you tried with "icons update" command?
Btw, thanks @birz4man for confirming this.

[NikosEfthias]

just issued that command and it broke vscode entirely vscode wont start

[NikosEfthias]

[NikosEfthias]

even after i uninstall extension from command line vscode is not working now

[robertohuertasm]

Reinstall vscode and all should be working again. Are you using Insiders version? Breaking when updating means something failed while restoring the backup. This command disables and enables again the extension by setting vscode to its original state and then applying again the extension patches.

[NikosEfthias]

I have both insider and normal but the extension is installed on normal
version

On Fri, Jul 29, 2016, 2:44 AM Roberto Huertas [email protected]
wrote:

Reinstall vscode and all should be working again. Are you using Insiders
version? Breaking when updating means something failed while restoring the
backup. This command disables and enables again the extension by setting
vscode to its original state and then applying again the extension patches.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robertohuertasm/vscode-icons/issues/113#issuecomment-236057397,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIrQ3ch8tSMvRA4j-P-2xmsaQbH0Xy4aks5qaT7egaJpZM4JW3Xs
.

[NikosEfthias]

i reinstalled it is fine now and i am using both insider and normal and extension is installed under normal one not insider

[robertohuertasm]

If you feel like it download the project and debug it in your vscode. I cannot reproduce it on my 15.04 and won't have access to 16.04 until next Monday. This is the way to go to know what's really happening.

[robertohuertasm]

When you say it's fine are you referring to your vscode or to the extension?

[NikosEfthias]

vscode is fine extension is still not working after reinstalling both vscode and extension but the update command just breaks everything

[robertohuertasm]

Just to be sure. You install the extension and restart vscode. Then run "icons enable" command, restart again and no errors in your console. If that's the case, debugging the extension is the way to go. If you can wait, I'll do it myself on Monday provided I can reproduce it. The strangest thing is that @birz4man seems to have the same settings and it's working for him...

[ScenK]

Same issue on Mac. Re-install the extension could work.

[robertohuertasm]

@ScenK I have a Mac and it's working (normal and insiders). Could you let me know what you see in the dev tools console? Did it work when you reinstalled it?

[ScenK]

@robertohuertasm Yes, it works after i reinstalled.

[jeffstahlin]

I just had the same issue on Ubuntu 16.10. My folder permissions for the /user/share/code were username:root which seemed to be fine until the latest update of vscode-icons, 1.5.5. I tried updating the icons, enabling them etc. but nothing worked. What fixed it for me was to change ownership of the /usr/share/code folder to username:username and then opening VS Code and enabling/updating icons (I did both).

[NikosEfthias]

updating icont broke my vscode entirely last time now let me try the group ownership hopefully its gonna work :)

[NikosEfthias]

nope it makes no difference @jeffstahlin

[jens1o]

Please give us the error code.

[NikosEfthias]

as i shared the ss before theres no error thrown
@jens1o

[robertohuertasm]

@NikosEfthias did you tried a clean install and then giving group ownership?

[NikosEfthias]

yes i even installed vscode from scratch

[robertohuertasm]

I've just tested it in Ubuntu 16.04, clean install and all seems to be working. Just to be clear, you say you reinstall the app, then do "icons enable", restart, and nothing happens, is that right? Can you send us a screenshot of your explorer tree?

[robertohuertasm]

Go to:

cd /usr/share/code/resources/app/out/vs/workbench

and look for workbench.main.css.bak and workbench.main.js.bak? Can you find those files?

[robertohuertasm]

just issued that command and it broke vscode entirely vscode wont start

If that's so this means somehow your bak files have not been restored properly. Delete VsCode folder and reinstall again.

[NikosEfthias]

here is the tree
update command
after restart
ownership of the folder
contents of the folder you asked @robertohuertasm

[jens1o]

Are they any errors in the dev console?

[robertohuertasm]

Can you send me your workbench.main.js and the bak file by email? roberto.huertas[at]outlook.com

[NikosEfthias]

what do you mean the bad file ? @robertohuertasm
and no there are no errors @jens1o

[NikosEfthias]

here you can see the file

[robertohuertasm]

It was .bak file... I was typing from a mobile phone....

[robertohuertasm]

@NikosEfthias it's strange. Your workbench.main.js is not modified at all... could you follow this steps and show me this file again after following them?

• Execute "Icons Disable" and make sure the .bak files are gone from the folder.
• Restart and execute "Icons Enable".
• Restart again.
• Send me workbench.main.js and workbench.main.js.bak please.

[jens1o]

@robertohuertasm Are you fully sure that you can catch up any permission denied error with the pattern in the main file? I think there could be some errorcode thrown that's actually not in the code.

[NikosEfthias]

now i am doing the instructions @robertohuertasm wrote above i will inform you shortly

[NikosEfthias]

here we go when i say icons disable vscode entirely wont open
this is how it looks

and the contents of the folder is here baks are gone

and the content of the main file is here

[NikosEfthias]

couple of errors

[jens1o]

Could you please uninstall any other extension via cli?

[NikosEfthias]

@jens1o what do you mean any other extension ?

[jens1o]

Do you have other extensions installed? @NikosEfthias

[NikosEfthias]

a couple that i use

[NikosEfthias]

i can try using insiders instead of deleting all other extensions

[jens1o]

Could you disable them, so we can be sure it is vscode that causes all these errors?

Edit: That's another option. Install insider and vscode-icons, and let us know.

[NikosEfthias]

is it possible to disable extensions without deleting on vscode ?

[robertohuertasm]

I don't think you have to disable anything. Let me see your files. The only extension modifying files is this one.

[jens1o]

Yes, it is possible.

Should I let you know how to disable them?

// Okey, roberto has the word.

[NikosEfthias]

@jens1o yes please let me know :)
@robertohuertasm what do you think the issue is ? i now downloaded insiders to try there

[jens1o]

Noo. Let's do what roberto says, he's the owner.

[NikosEfthias]

@jens1o i just wanna know how do i disable something its not about the icons :) some very useful extension becomes painful in big project folders so i can temporarily disable them

[jens1o]

Oh, I have to changed my output. It is not possible. I thought because you need to enable then once you've installed it, it is available. But it isn't....

[robertohuertasm]

I'm not really sure at the moment. What i can see is that the workbench.main.js file is not being modified, which would indicate some lack of permissions but you're not receiving any warning and the replace function doesn't write into your console, which is weird because if the modification would fail you should have a message there... so let's do something:

• Reinstall your vscode
• Be sure that you don't have any .bak file in the folder
• Uninstall the extension (restart and all the stuff).
• Check out again the folder: no .bak files should be there.
• Install the extension (restart, blah, blah)
• Execute _icons enable_ but before restarting check the console for errors.
• Share with us the errors (if any) you have found and these files: workbench.main.js, workbench.main.css, workbench.main.js.bak and workbench.main.css.bak

Then, provided that you still have some errors, we'll analyse those files to find out what's happening.

[jens1o]

@robertohuertasm Are you fully sure that you can catch up any permission denied error with the pattern in the main file? I think there could be some errorcode thrown that's actually not caught in the code.

[robertohuertasm]

Any non controlled error regarding permissions should be logged into the console.

[NikosEfthias]

i just now installed insiders and installed the extension seems working for insiders let me try all you wrote above @robertohuertasm

[NikosEfthias]

from insiders

[jens1o]

Great!

[robertohuertasm]

Cool, I already tested it yesterday in Ubuntu 16.04 and for me was working in both versions.

[jens1o]

Looks not like that's a bug. Looks like there are problems with users.(No, I'm not inpolite to anyone.)

//vote4close

[NikosEfthias]

after i purge apt-get purge noticed that the resources folder was not deleted by apt hopefully deleting it and fresh install will fix the issue

[robertohuertasm]

Stable version is not really different from insiders in terms of what we currently do to make the extension work so a clean install should be working.

[robertohuertasm]

@jens1o We should know what's happening to @NikosEfthias so we can help some other people who may find the same issue. Even more, we maybe can prevent it if we knew how they make it to crash the extension in the first place. So I vote to keep it open until @NikosEfthias checks out whether the clean install works or not for him (hopefully yes) :wink:

[NikosEfthias]

here we go :+1: it works after deleting the resources entirely the problem was i think resources were never updated and still its weird that extension didn't update the file though its owned by me whos the same user running the vscode

[NikosEfthias]

so i guess the issue can be closed :smile:

[NikosEfthias]

thank you so much for help finally got the icons back :)

[robertohuertasm]

Ok! So we've learnt that in case that a clean install does not work we have to manually delete the resources folder to start afresh.

[NikosEfthias]

exactly

[robertohuertasm]

This is coming from the duplicate #161.
@jorawarsingh can you check your dev console for messages? Can you attach a screenshot of your tree view? Have you checked that you're not behind a proxy?

[jorawarsingh]

thanks for helping me @robertohuertasm Here i the screen shot.

No i'm not behind proxy.

[robertohuertasm]

@jorawarsingh have you executed the "icons update" command? => F1 > Icons Update

[jorawarsingh]

now that's was tricky i got updates in the extension panel and updated from there may be three times and never worked what's the different? I have icons now :+1:

[robertohuertasm]

I'm glad it's working for you know. The latest update supported auto "Icons Update" command execution but somehow yours wasn't working. You always must run this command whenever it's a new installation or update of the extension or vscode.