I am been fighting with TigerVNC since around Fedora 17. Every time I started it manually I would get a black screen that would eventually display the gnome desktop and if I started with systemctl it would not work at all.
Recently wiped my system and installed Fedora 30. Same black screen when I manually start vncserver, but now it never displays the gnome desktop.
These are all default installs. I get no errors to accompany the black screens. I am at a loss of what to do. Could someone provide a working xstartup, config, and command line vncserver command so that I can hopefully get this working?
I had the same issue today after a fresh Fedora 30 install.
But, my home directory is from an older install so I'm using my old ~/.vnc directory and ~/.Xclients file.
I got it working by doing the following two things:
sudo echo "DESKTOP=GNOME" > /etc/sysconfig/desktop
Start vncserver manually as yourself. If you are already running a desktop on your system then you will have to use a different display number, so the command would be something like "vncserver :2".
Related
I am running Cygwin64 on two Win10 machines, one Home and one Pro. My software uses tftpd to receive a CSV from a network peer. tftpd is run from init (package sysvinit) with this line:
td:2345:respawn:/usr/sbin/tftpd -vvvvv -L -c -p -u Larry -U 000 -s /tmp
There is no xinetd running, no xinetd or tftp configuration file that I know of. On the Win10 Home system, which is my development system, this works. On the Win10 Pro system, it fails. The client times out. There is no entry in /var/log/messages (syslog-ng). Windows Application Log says "Cannot drop privileges: operation not permitted"
When I stop init and run that command line in a shell, it works and clients can transfer files in. But my system needs the respawn management of init. The pattern was set 12 years ago with Cygwin32 on Win7. My customer is now updating the PC and we have this glitch. If I were developing now, I would put the function on a raspi, but this is just a PC change.
Can anyone recommend a configuration to get the execution of tftpd under init under cygwin under Win10 Pro closer to that of the same command line in a user shell?
Edit 1: I also tried suid. tftpd.exe is owned by the user account, not SYSTEM or whatever cygwin has for root. Suid does not set permissions in a way that solves the problem.
Edit 2: adding cygdrop to the inittab line does not help.
Guess this one will be another tumbleweed. I found no good answers in 3 days of grinding. The problem seems to involve domain vs. local users in Windows, and how Cygwin interacts with the Windows user database, whatever that is. I ended up running the tftp server in an infinite-looping batch file that starts at user login, but is vulnerable to somebody killing the top level shell. Along the way, I recompiled tftpd-hpa for Cygwin and commented out the user ID change - that worked on my PC but not the customer's. If they have problems with the solution I may just retarget to raspi.
https://i.imgur.com/hYf1Bes.jpgm
I am trying to set up ROS and Gazebo in a VM running Ubuntu.
The goal is that I want to simulate Turtlebot with the open manipulator.
I installed everything without any issues.
Though I am not able to launch the Turtlebot environment on Gazebo (like here: http://emanual.robotis.com/docs/en/platform/turtlebot3/simulation/)
$roslaunch turtlebot3_fake turtlebot3_fake.launch
results in Gazebo staying forever in the state loading your world. After some time, it stops responding.
Launching the empty world however works.
I am using ROS 1 with Gazebo 7.0
My hardware setup:
MacBook Pro 13" 2019 with 16 GB RAM
Parallels VM: 3D virtual. ON, no performance limit, 4 CPU kernels, 12 GB RAM enabled
Thank you so much for your help.
After every change you made source your bash and make sure to run :
catkin make
if you've done this already then check if ros is installed properly by running
roscore
on one terminal and let it stay running.
After that try to launch your turtlebot on another terminal.
If it doesnt work even you have installed all of the needed things, i think the problem is with your VM, id recommend you to run ROS on Ubuntu running USB Stick.
cd ~/.gazebo/
mkdir models
cd models/
wget http://file.ncnynl.com/ros/gazebo_models.txt
wget -i gazebo_models.txt
ls model.tar.g* | xargs -n1 tar xzvf
try this gazebo try to download to packages that's why it waits u need internet for that this may take few mins
I am trying to flash my google coral dev board on the macos. I learned that Catalina wouldn't function for using the board, so I downgraded to Mojave. Everything goes smoothly, except when I type the command
bash flash.sh
Onto my terminal in the process of flashing my board. The terminal returns the command:
Couldn't find fastboot on your PATH -- did you install it?
I am sure I installed it. When I type fastboot devices or version on my terminal, it shows up correctly. And, when I echo path, this comes up
/Users/name/Downloads/fastboot:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
So I am sure that it is on my path also. Does anyone know the solution to this?
Try opening a new terminal and see if it is still in your path. If it is not in your path you can add it to ~/.bash_profile
sudo vim ~/.bash_profile
Add the line:
export PATH=${PATH}:~/.local/bin
Then when you open a new terminal it will still be in $PATH and bash flash.sh should work
I faced the very same issue as you, and the way I could run flash.sh to "flash" my Coral dev was by modifying the file (flash.sh) and added the path where fastboot was located.
(I'm a Mac user) This is how I did it:
I went to check the version of fastboot (It also gives you where is the file located at)
cd ~/.local/bin
then:
./fastboot --version
Command results:
fastboot version 30.0.4-6686687
Installed as /Users/jegamboafuentes/.local/bin/./fastboot.
Then I went to the flash.sh file, open it and modify the line 19:
FASTBOOT_CMD="$(which fastboot)"
for:
FASTBOOT_CMD="/Users/jegamboafuentes/.local/bin/./fastboot"
I re-run, and BOOM! it worked, my Coral Dev Board was flashed.
Check your model number using the reference here. If it was manufactured before April 10, 2019, then there are some steps for you to follow.
Similarly, make sure you download the latest fastboot version here. Fastboot should be version 28.0.2 or higher. Hope this helps.
I have a bug with Yarn and terminal (on Windows 10). When I use yarn add, yarn start etc then the first several lines are invisible and empty space appears.
For example, I have test.js with console.log('Hi console').
When I use yarn start (screen 1).
When I use npm start.js - it's ok. And then If I use yarn start - it's ok too. (screen 2).
But using 'yarn' standalone - making this bug.
Also I tried reset. Did not help.
So, it is March 2020 and I encountered this problem with Yarn 1.22.1, running VS Code Insiders on Windows 10. The OP's screenshots above show the problem, with the version of Yarn printed, followed by rows of empty space before returning to the prompt after apparently ignoring the command.
According to vscode issue #72145, "This is a bug in Windows 10 1809, unfortunately we have no way to work around the issue so you will need to wait until you get the next version of Windows 10 (1903)" ("Tyriar", April 11, 2019).
The fix the terminal in VS Code for me was to upgrade to Yarn v.2, which was just released in January 2020.
Yarn 2 has a lot of differences to Yarn 1, however, so you would want to read the Yarn 2 Migration docs before deciding if upgrading is the best course of action for your project. The chunk of empty space still appeared after upgrading, but was followed by the correct output in response to the Yarn commands.
Before upgrading to Yarn 2, if you don't want to do that yet, the workaround was to open the Windows 10 Command Prompt, cd into the project directory, and run the Yarn commands from that CLI. Using the Windows CLI correctly showed the correct output to Yarn commands where Git Bash did not.
Hope this might help someone.
I am trying to run any GUI container I can on MacOS. With every container I try (firefox, chrome, tor, spotify, etc) I always get the error Error: cannot open display. And it's not specific to the docker run command where I pass the environment flag with my $DISPLAY. When I try to run xhost + I get the same error.
I have a fresh XQuartz installation. It is up and running. I have turned on "allow connections from network" under security. I've tried building my own images and pulling jessie frazelle's images. I do not suspect it is a docker issue or the Dockerfiles. It is something on the host, my laptop. I can't seem to figure out what it is.
MacOS Sierra 10.12.5
Docker 17.12.0 Stable
XQuartz 2.7.11 (xorg-server 1.18.4)
My local's $DISPLAY is set to :0.0
So I finally got this to work. And it seems it was pretty simple. I am not certain how this actually fixes the issue, but now the containers work.
How I fixed it was opening up XQuartz and then opening up the "Terminal" app from the "Applications" menu. Then running the command export DISPLAY=192.168.1.X:0, then xhost +. It outputted something like this "access control disabled, clients can connect from any host". After that I was able to run my docker run commands to launch the desired GUI containers.
I am still uncertain how this works and not running them from my laptops Terminal app, but it worked. It must be something I have set in my local env. Hopefully this helps someone else out who may be running into the same issues.
Based on #Byron's answer, I've found out that I could get it to work by running these 2 commands in the normal terminal:
export DISPLAY=:0
/opt/X11/bin/xhost +