I opened an ubuntu virtual machine on gcloud and tried to install GUI(window-user interface) I installed Xfce with
apt-get install xfce4
command. But
i get
no screens found(EE)
error.I tried "gnome" "KDE" but same result and i don't know why. I searched online and tried everyway as ı know but no success.
The full error is
current Operating System: Linux instance-5 4.13.0-1008-gcp #11-Ubuntu
SMP Thu Jan 25 11:08:44 UTC 2018 x86_64 Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.13.0-1008-gcp
root=UUID=b6adc449-5e3d-4331-ba6b-6e99a75fa48e ro
scsi_mod.use_blk_mq=Y console=ttyS0 Build Date: 13 October 2017
01:57:05PM xorg-server 2:1.18.4-0ubuntu0.7 (For technical support
please see http://www.ubuntu.com/support) Current version of pixman:
0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 30 12:24:29 2018
(==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE)
Fatal server error: (EE) no screens found(EE)
Why i am getting this error? Is this because of gcloud servers or something else?
Please help.
At present there is no GPU installed on any of the VMs and having a graphical desktop on them is not so straight forward. There is a GPU feature request which you can follow by pressing on the star on Public Issue Tracker (PIT) link.
To be able to have and use a graphical desktop you can configure VNC remote access for your VM as described in the URL links 2 and/or 3.
Keep in mind that although above link 2 or 3 steps seem to have succeeded, these are third-party websites containing information that isn’t provided by Google and its contents cannot be guaranteed. Also since there is no GPU installed, this installation might fail for high resolution desktop.
Related
I'm using WSL2 on Ubuntu 18.04 to run Ruby code in Windows 10.
For example, running Ruby on Rails is easily done with no special setup required.
In case of Ruby2D:
The installation went fine but, I get an error when running any Ruby2D file, even the most basic one:
require 'ruby2d'
show
I get this error in Console:
error: XDG_RUNTIME_DIR not set in the environment.
Error: (SDL_Init) No available video device
error: XDG_RUNTIME_DIR not set in the environment.
Error: (SDL_CreateWindow) No available video device
Error: (GL2 / SDL_GL_CreateContext) Video subsystem has not been initialized
Error: An OpenGL context could not be created
How do I "add" (or config) a "video device" to my Ubuntu on the WSL2?
As you've noticed, WSL under Windows 10 doesn't have any GUI/X/windowing capabilities built in. There are a few possibilities:
If you have the ability to upgrade to Windows 11, it supports WSLg (built-in) for running Linux GUI apps directly on Windows. I did just install Ruby, ruby2d (and its dependencies) and was able to successfully execute your example. I assume it is just supposed to show a blank GUI window ...
If you can't upgrade to Windows 11, there are still several possible alternatives for running Linux GUI apps. I have not had a chance to test ruby2d in this type of environment, but I believe it should work. If you run into issues, I can at least get the first option up and running to try it out and see if we can work through it:
First, my preference is to install xrdp and a simple window manager like xfce. See my answer here for details and instructions. You don't need the full Gnome environment (which requires Systemd) - A simple installation of Xfce should do.
However, the most popular method is to install a third-party X server on Windows 10 and set up the DISPLAY variable manually. If you'd like to go this route, see this question and its answer for details.
I'm trying to test my development environment and keep getting this error while going through the "Building Your First Network". I've installed the prerequisites on a Windows 10 Home edition so I'm using Docker Toolbox. The error is described as follows and happens just after a execute the ./byfn.sh up -l node command:
2019-11-14 17:06:26.982 UTC [msp] loadCertificateAt -> INFO 002 Failed loading ClientOU certificate at [/var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem]: [could not read file /var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem: open /var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem: no such file or directory]
As you can see there is a backslash just before the ca.example.com-cer.pem which I think is causing the problem. Anyone have an idea of how I might solve this issue?
Docker Toolbox for windows doesn't provide a great experience for users. It's limited in how it can share windows directories with linux containers running in the linux VM it creates. I believe it can be made to work but you have to use very specific folders in your home directory and you would have to google it to find all the details but it's a lot more of a hassle.
You have other options of course
Upgrade to Windows Pro and use Docker for Windows (which doesn't have the same sharing limitations, but still not a great experience and you can still encounter problems sharing the directories)
Install a hypervisor such as virtualbox and run a linux desktop distribution such as ubuntu or mint and use that instead (which I would recommend and would suggest ubuntu 18.04 mate edition)
Wait until next year when hopefully microsoft will release WSL2 for everyone (including home edition) and then Docker won't need a linux VM running and it should be a much better experience trying to run linux containers on windows.
As mentioned by lindluni here
Backslash problem in Hyperledger 2.0.1 when orderer/peer look for .pem files
the problem arises when one creates crypto artifacts under Windows since "golang filepath.Join uses the current OS's filepath scheme". Hence, under Windows backslash is used in all the generated config.yaml files found in crypto-config/*. One can replace this backslashes before the deployment to fix the issue.
I am having a difficult time getting native script up and running with the cli.
I followed the setup script which does everything for you. I did this on node 4.4.6. Which is listed as stable for right now.
Earlier I had attempted this on 6.2.1 as well.
I have xCode running and I followed allowed the start up script to do all of the installs on 4.4.6. With 6.2.1 I did the set up manually.
In both cases I am getting the a successful build message.
** BUILD SUCCEEDED **
Project successfully built.
Using /Users/steven/projects/nativescript/conf2/confRps/platforms/ios/build/emulator/confRps.app
Starting iOS Simulator
Immediately followed by SecTaskLoad
Jun 24 15:11:53 jays-MacBook-Pro backboardd[34043]: SecTaskCopyDebugDescription: confRps[40147]
Jun 24 15:11:53 jays-MacBook-Pro backboardd[34043]: SecTaskLoadEntitlements failed error=22 cs_flags=200, task->pid_self=-1
Jun 24 15:11:53 jays-MacBook-Pro backboardd[34043]: SecTaskCopyDebugDescription: confRps[40147]
Jun 24 15:11:53 jays-MacBook-Pro backboardd[34043]: SecTaskLoadEntitlements failed error=2
I am getting an the iphone emulator to appear but nothing is working with the current buttons I have installed.
I know others have installed native script wondering what things I need to look for in debug this issue?
This answer might help you to solve your problem, however it would help if you give some more info about the problem and NativeScript version. In regard to that in case you want to use old project it would be good idea to remove the platform with tns platform remove ios and to add it again tns platform add ios.
I am running Angstrom ( v2012.12) on my BeagleBone Black (Linux beaglebone 3.8.13 #1 SMP Thu Sep 12 10:27:06 CEST 2013 armv7l GNU/Linux). I am using the following gcc:
COLLECT_GCC=arm-angstrom-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/arm-angstrom-linux-gnueabi/4.7.3/lto-wrapper
...
gcc version 4.7.3 20130205
I needed to install some library on BBB and while running the script I got this error: "gcc: error: unrecognized command line option -m32". After googling around I figured out that I need a cross compilation to be able to do that (I hope that is the right way, perhaps I am doing something wrong). I started looking for the appropriate toolchain: angstrom-eglibc-i686-armv7a-vfp-neon-v2012.12-toolchain.gz, but I did not find too much. Since http://www.angstrom-distribution.org/toolchains is still out of order I only found a few place where I could get the archive, but it was corrupted.
So my questions are the following.
Am I correct with all this cross compilation stuff, would it help we to solve my problem?
If I am on the right track can somebody share a toolchain packet or give a valid link.
I would really appreciate any help. Many thanks in advance
I found a workaround to that problem. Eventually I adjusted the installation script to omit undesired options ("-m32" in this case) and it worked.
I had been running Fedora 9 for the last year --- I have a Windows box (actually a VM) that mounts a folder on the Fedora box using my own name/password. I do this so that I can run my version control program (Vault) on Windows. It has worked flawlessly for the last 6 months.
Yesterday, I upgraded Fedora from version 9 to version 11. Since doing so, I am no longer able to change file permissions from my Windows box. Nothing has changed, there's no firewall on the machine, SELinux is disabled (SELINUX=disabled in /etc/sysconfig/selinux), etc
I can still read the files. Any idea what has happened and how I might fix this?
Thanks,
David
P.S. The error I get is
An error occurred applying attributes to the file:
....my filename...
Access is denied.
P.P.S. I AM able to create a NEW file in the mounted folder. After doing so, I can change its properties to make it be read-only. BUT I then can NOT change its properties again to be writable. Hope this helps.
Turns out this would appear to be a bug in the latest version of Samba that you get when you install Fedora 11.
I manually built SAMBA 3.4.1 from source, installed it and my Windows machines work just fine with it.
(Just in case anyone else searches this site)