Nothing in the paper is revolutionary, but it puts the pieces all together nicely.
Some VNC functionality was broken in Ubuntu 14.04 due to Vino, but fortunately, it’s fixable:
Using a combination of clues from http://discourse.ubuntu.com/t/remote-desktop-sharing-in-ubuntu-14-04/1640 (which is all about VNC access) and https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1281250 (which discusses the bug introduced into Vino) I have managed to resolve the matter.
Essentially you have to disable encryption on remote desktop access in Gnome due to a bug that has come to surface in Vino. However, some threads tell you to uncheck it in the wrong place. Follow these guidelines and you should be able to resolve it quickly.
dconf > org > gnome > desktop > remote-access > require-encryption – uncheck
dconf > desktop > gnome > remote-access > enabled – uncheck
Here is how you do it:
Desktop Sharingis set up properly.
dconf-toolsby typing in Terminal
sudo apt-get install dconf-tools
Require Encryption(don’t click on Set to Default as it rechecks it)
It should now work. Tested through a reboot and all good.
Hope it helps.
(I have got a screen shot of dconf but don’t have enough points on here to post it – I am sure everyone can work it out for themselves though! 🙂 )
Now this is the best way to play darts. 🙂
Tanya Short gave one of the best talks I’ve heard in a long time about the fallacies of crunching and bad work habits many people have. The video is now up for free at the GDCVault. Her talk starts at 6:00 :
Summary of her points:
When trying to hit deadlines, she starts out by observing that most of the time we think ‘getting X done’ is our highest priority. It’s not. It’s actually #3:
Your real priorities:
That sounds great, but it also sounds a bit idealistic. She says it is not easy, but lays out these points.
Step-by-step roadmap to not dying:
A few long nights won’t kill you, but a few long months might. Especially if combined with other health and life factors.
Burnout is the feeling of being dulled as layer after layer of exhaustion accumulates. Burnout is the void left behind where your career could have been.
Then she has a real Benedictine moment: The moment right now will never come again. Every one of us will die. No matter what we create, all we have is right now. Don’t use up that joy, love, and creative energy you have by burning yourself out.
Keep death always before your eyes.
—St. Benedict: The Rules: Chapter 4.47
She doesn’t cite the studies, but I found some:
Setting up VNC on Ubuntu used to be pretty painless. But recent changes in Ubuntu and X have left it kind of a mess. It took me way longer to set up VNC than it should have, and finding the documentation wasn’t super-easy either. There were lots of broken guides. So, here’s what you need to do:
I was trying to scp some files and kept getting this:
scp: connect to host 134.xxx.xxx.xxx port 22: Connection refused
Some linux distros, like the ancient Fedora 21, have ssh daemon turned off by default. So, turn it on:
sudo service sshd start
Lets say you want to copy between two hosts host_src and remote_machine. host_src is the host where you would run scp, ssh or rsyn, irrespective of the direction of the file copy.
Your public key has been saved in <your_home_dir>/.ssh/id_rsa.pub
If this file does not exists, then the above cat command will create it. Make sure you remove permission for others to read this file via chmod. If its a public key, why prevent others from reading this file? Probably, the owner of the key has distributed it to a few trusted users and has not placed any additional security measures to check if its really a trusted user.
Optional – allowing root to ssh:
Thats it. Now you can run scp, ssh and rsync on host_src connecting to remote_machine and it won’t prompt for the password. Note that this will still prompt for the password if you are running the commands on host_dest connecting to host_src. You can reverse the steps above (generate the public key on remote_machine and copy it to host_src) and you have a two way setup ready!
This was more annoying than it should have been. When setting up my Amcrest IP2M-841B camera, I was able to use the Amcrest IP Config tool to log in and watch my camera without issue.
When using iSpy 64, however, the darn thing couldn’t figure out how to connect to it. Here’s how I did it. I left the camera on channel 1, set the encoding to plain H.264, and then did the following.
The first thing is to make sure your camera is working at all:
If connecting via VLC worked, your 75% of the way there.
Once you have iSpy connected, you can set up events and connect to the cloud for full web monitoring.
So, where did I get that rtsp line? Directly from the Amcrest HTTP API SDK Protocol Specification. Section 4.1.1, p14 – Get real-time stream. It’s also a handy guide on all the other parameters you can send the camera.
Windows can trigger this error, but sometimes it’s not easy to figure out what’s going on.
I recently got this error when trying to use the OpenGL ES ANGLE library on Windows 10. When compiling against the ANGLE library, the error came when trying to call into the ANGLE and used eglGetProcAddress().
eglGetProcAddress() returns function pointers for important GL extensions, so I couldn’t just ignore it or work around it.
In looking around, the obvious first step is to make sure you’re defining the function pointers correctly, but that turns out not to be my problem.
In looking at this article, I realized I probably had a mismatch of compiler and linker settings. The Visual Studio projects (VS2008) that came with ANGLE required a certain set of compiler and linker flags that were not standard. I had migrated the Visual Studio projects to VS2015, so that also added an element of uncertainty. I simply opened both project settings up next to each other and compared the settings for the ANGLE library build and the final project and found a few mismatches. I change a number of them to be the same, and things worked great.
Check the linking AND compiling flags for not only your project, but the project files that generate the libraries you’re linking against. Differences in compiler settings can cause this error.