I downloaded and extracted VS Code in a Debian x64 VM and tried to run it. It complained about missing glibc libraries (I have 2.13, it needs 2.15). I followed these steps to get Ubuntu DEBs. Using those, VS Code throws a segmentation fault when I run it. gdb tells me:
linux_test_for_tracefork: waitpid: unexpected status 11.
Why won't Visual Studio Code run for me in my Debian VM?
Updating to Debian 8 fixed this problem.
Related
I was using Cygwin 32bit.
I recently had a problem with my PC and I'm trying to reinstall Cygwin 32bit.
"cygwin is not supported on 32-bit windows"
Couldn't install with message.
So, I installed Cygwin 64bit and built my project.
However, an error occurred at line 102 of the usr/include/cygwin/signal.h file.
It looks like the problem is that x86_64 is not defined, how can I fix it?
Answers I'll wait.
hello!
I was using Cygwin 32bit.
I recently had a problem with my PC and I'm trying to reinstall Cygwin 32bit.
"cygwin is not supported on 32-bit windows"
Couldn't install with message.
So, I installed Cygwin 64bit and built my project.
However, an error occurred at line 102 of the usr/include/cygwin/signal.h file.
It looks like the problem is that x86_64 is not defined, how can I fix it?
Answers I'll wait.
Installation vscode
I'm running Arch Linux (Manjaro) and installed vscode with:
sudo pacman -S code
but then a simple .NET core program resulted in
--------------------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (clrdbg) with Visual Studio
Code, Visual Studio or Visual Studio for Mac software to help you develop and
test your applications.
--------------------------------------------------------------------------------
It seems like the official Microsoft build should be obtained via the snap store:
sudo snap install code --classic
And the program looks normal. I can install plug-ins, create a new file et cetera.
Problem
However, I cannot open any files or projects. Doing so results in vscode crashing. I read that code --disable-gpu could solve this problem, but doesn't do so for me.
Any ideas
what may cause this crash?
or how to get the pacman vscode working?
Logs
$ code --verbose
Gtk-Message: 22:59:19.805: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:59:19.805: Failed to load module "canberra-gtk-module"
(code:33833): GdkPixbuf-WARNING **: 22:59:19.817: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
This likely means that your installation is broken.
Try running the command
gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
[33863:1104/225919.911481:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[main 2020-11-04T21:59:19.960Z] Sending env to running instance...
[main 2020-11-04T21:59:20.041Z] Sent env to running instance. Terminating...
[main 2020-11-04T21:59:20.041Z] Lifecycle#kill()
where the recommended gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache results in bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: No such file or directory
I'm running Arch Linux (Manjaro) and installed vscode with:
sudo pacman -S code
but then a simple .NET core program resulted in
--------------------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (clrdbg) with Visual Studio
Code, Visual Studio or Visual Studio for Mac software to help you develop and
test your applications.
--------------------------------------------------------------------------------
I had the same issue trying to get the debugger to work and I spent hours on finding the reason for this. What I found out is that the debugger only works with officially signed Microsoft binaries of VSCode. So you have to make a distinction here:
The package code contains the open source version of visual studio code, a build wich anyone can make using the provided sources by Microsoft. The program which you get here is therefore not signed by MS!
The package visual-studio-code-bin provided by the AUR contains a officially signed version by MS. If you use this package, the debugger works as expected.
I do not know wether snap - which I personally never used at all - provides this kind of package, so I can not tell anything about that, but using the said package from the user repository solved the problem for me reliably.
Try this one (which I installed just yesterday under the recent manjaro distribution and it worked fine) and see if this solves your problem with opening files and folders.
I've downloaded Realm Studio from here. When I opened for the first time it asked me if I wanted to integrate it into my system. I clicked on Yes and from there nothing. I can't open the App and if I launch it from terminal I see only
segmentation fault (core dumped)
This happens also with version 2.8 and with the .tar version (Nothing happens if I click on the icon in the extracted archive and the same message if I try to run it from the terminal).
I'm running Ubuntu 18.10 64bit. Thank you all for the help.
I don't mean the version(s) provided by the various distributions but the binary from the official website.
I have an old VM running 32bit OpenSUSE 12.1 that is configured for a project I'm working on at work. I need to install WebKitGTK. The problem is that the cmake in the repositories is ancient 2.x, while WebKitGTK at least 3.6 (or similar). So I went to the official website and (my fault) without looking too much into it downloaded the 3.10 installation for Linux.
Upon executing the binary that was installed I got the error that the file could not be run. I checked the execution rights and it was fine. Then it struck me...I ran file cmake and got 64 instead of the required 32bit.
I went back to the website and all I could find were 32bit versions for Windows but none for Linux.
I can build it from source but just out of curiousity would like to know if support has been dropped. I was unable to find any information so far.
32-bit support for CMake hasn't been dropped. They just don't provide binaries for it on their website as of CMake 3.7.0
here's my system specs;
Arch Linux x86_64,
Kernel: 3.6.10-1-ARCH,
Gnome 3.6.2,
xf86-video-nouveau 1.0.4-1,
jdk7-openjdk 7.u9_2.3.3-1,
jre7-openjdk 7.u9_2.3.3-1,
jre7-openjdk-headless 7.u9_2.3.3-1,
lib32-libjpeg-turbo 1.2.1-1, libjpeg-turbo 1.2.1-1, libjpeg6-turbo 1.2.1-1
libpng12 1.2.50-2,
net-tools 1.60.20120804git-2,
unzip 6.0-6.
Ok, so there's the list of requirements that are installed, version numbers as well. Upon launch, the loading/splash screen won't even show, and then nothing... it just dies out. I attempted to launch it "aptana -v" and no output in the shell. I have looked for any error logs in ~/ , but nothing is there.
Other steps I've done is to delete any configuration folders/files for eclipse and aptana-secure in ~/. Also did a clean uninstall of just Aptana (not the dependencies), reinstall. Same result.
Any suggestions?
It appears that there is a mix up in the downloads. 32-bit and 64-bit got switched. If you are on 32-bit download 64-bit and vice versa. Hopefully it will be fixed soon.
See issues below:
Aptana 64 bit version crashes on startup on 64bit Linux OS with 64bit Oracle 7 java
Linux Installer Aptana_Studio_3_Setup_Linux_x86_3.3.0.zip contains x64 bit version of the project