I have a problem with VSCode and my virtual network drive.
The drive is a SFTP drive mounted with Expandrive 5.0.15.
The problem appeared when i try to open a folder with VSCode but not when i open a single file.
So I don't know what is the problem but there is an error with Node, I guest...
Does someone have an idea ?
Maybe an encoding problem ?
The SFTP server running on Ubuntu and I'm on Windows 10.
Thanks
Related
Can someone explain to me why Phing cannot read the xml file under Windows wsl2 access using PHPStorm
screenshot
I am new in Linux (Ubuntu 20.04 WSL) and I got a problem hopefully you can help me.
I can create a file from PhpStorm like index.php or anything, but I can not oversave an existing file. The message is
Unable to save settings. Failed to save settings.Please restart PhpStorm.
I tried switch off Windows Firewall, but did not work.
I did reset a few times WSL and reinstall PhpStorm but did not work.
The Notepad++ can save files to the shared folder (user/Jon/.azure).
try to set to login in wsl as root from CMD terminal -> ubuntu20 config --default-user root
I use Android Studio on my PC and my Laptop. My projects are stored in Google Drive, but Google Drive is in different places on the PC and laptop.
I just edited a project on my laptop, now I try and run the emulator on my PC for this project and I get an error as it's looking for some things in the location they were on the laptop.
04/23 10:34:51: Launching app
$ adb install-multiple -r S:\Google Drive\AndroidProjects\Connect3\app\build\intermediates\split-apk\debug\slices\slice_0.apk S:\Google Drive\AndroidProjects\Connect3\app\build\intermediates\split-apk\debug\slices\slice_5.apk C:\Users\AndyC\Google Drive\AndroidProjects\Connect3\app\build\intermediates\split-apk\debug\slices\slice_2.apk...
$ adb shell pm uninstall com.androidandyuk.connect3
Unknown failure (at android.os.Binder.execTransact(Binder.java:565))
Error while Installing APKs
The S drive is where they are on PC and C is on the laptop.
How can I fix this?
Thanks.
Whilst I thought adding in Github would only help me going forward, it must reformat the code to work independent of your own file system as I was able to edit it again.
I've been trying to download a tar file from the internet on a remote machine using Linux (and PuTTY), but nothing has been working for me. I was able to download it on my Windows laptop, but I can't figure out how to either transfer from my laptop to the remote machine or just download it from PuTTY. Does anybody have any ideas?
my environment:
kubuntu : 3.2.0-generic-pae
vmware player: VMware-Player-4.0.4-744019.i386.bundle
And i have been installed it.
$sh VMware-Player-4.0.4-744019.i386.bundle
I have a problem, when i launch "menu->system->VMware Player"
it launch a window and start compiling:
[ok] Virtual Machine Monitor
[failed] Virtual Network Device
[ok] VMware Blocking Filesystem
[ok] Virtual Machine Communication Interface
[ok] VMCI Sockets
[result fail]Starting Vmare Services
See log file /tmp/vmware-root/modconfig-2722.log for detail
from log file:
[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences"
No such file or directory.
Failed to find /lib/modules/preferred/build/include/linux/version.h
Failed to compile module vmnet!
Could some people tell me what's wrong ?
I suppose that there are no linux headers installed on your machine, that is why it is impossible to build the vmnet module. You must install headers and then try once again.
Ok, I've had the same problem this evening when upgrading from 4.0.3 to 4.0.4. What I've found to work is to first download the patch from this VMWare community thread - http://communities.vmware.com/thread/344213
Unzip it and then open the patch-modules_3.2.0.sh in gedit. There will be three lines at the top that read:
fpatch=vmware3.2.0.patch
vmreqver=8.0.2
plreqver=4.0.2
You have to change the plreqver=4.0.2 to plreqver=4.0.4
Then, open your terminal and run
sudo ./patch-modules_3.2.0.sh
As a side note, keep that file handy, because I found that I had to do the same thing when upgrading from 4.0.2 to 4.0.3 in Ubuntu 12.04. However, when you try the same again in the next upgrade (e.g. change the plreqver to 4.0.5 and run the script), it will say that the file is already patched and it won't work.
To get around this, you need to go to the "/usr/lib/vmware/modules/source/" folder, find the hidden file called ".patched", and delete it (easiest option is to "sudo nautilus" in terminal and hunt through the folder structure). Then it thinks that it hasn't been patched and does the process again.
Hope this gets your VMWare back up and running.