I decided it was time to check out Star Citizen for Alpha 3.0. I created an account, paid my money, and downloaded the launcher. I was greeted with this:
Electron! Cool! OK, so what now? I googled around a bit and searched the forum to see if anyone else was experiencing this. Nope, just me.
I tried uninstalling/reinstalling and rebooting in various combinations. I tried it on another computer in my network and it worked normally.
What should have been obvious somehow wasn’t. I went to bed.
With a fresh mind I reviewed the evidence. The error was screaming the answer to me the whole time.
Failed to load resource: net::ERR_CONNECTION REFUSED http://localhost:9000/app/cig-launcher.js
Chrome dev tools were open
All of a sudden it clicked – I’m in development mode! Doing node development on that machine I had set the environment variable NODE_ENV to Development. Removing that environment variable was the solution.
I don’t like typing “nautilus” to open the folder explorer from the terminal. Mac’s “open” command is shorter and makes sense to me. To get the same command in Ubuntu, we just have to add it to bash aliases.
Open up ~/.bash_aliases to be edited. I usually use nano.
Add this line
When using the terminal, to open nautilus in the current folder, you can run this command
open . &
The “&” detaches the process from the terminal and is optional.
Reflecting back, the only time I’ve ever done something right the first time is when it wasn’t my first time doing it.
As a contractor, I encounter eerily similar situations at most places I involve myself with. Even businesses not in the same industry. Most businesses are trying to solve similar problems across multiple domains with slight variances. This is exactly the reason learning design patterns is a good investment of your time.
If I’ve ever come into a new project and nailed it on the first try, it’s only because I recognized the similarities from a previous project, employed the things that worked, and avoided the things that didn’t.
From the perspective of full time employees, it’s a challenge to be allowed to fail a few times at one employer. A contractor can have a few “challenging” gigs and then stumble upon the perfect redemption project for a win. A full timer would have to get a rare blessing from above to rewrite something for the third time.
Build something small and scale it
The axiom “build something small and scale it” is a great strategy. The problem is knowing exactly how something will scale. Users have a way of turning your well thought out schema on it’s head. Still, something small is far easier to rewrite. Build something small, release something small, rewrite something small, release a rewrite of something small, and scale it is not as fluid off the tongue. It’s more accurate, though.
I had an issue that came about suddenly while working. Every now and then my cursor would jump to the upper right corner and lock to the taskbar. I couldn’t find any pattern to explain it. I tried:
activating/deactivating the trackpad
swapping my mouse out
cleaning my touchscreen
The issue persisted. I noticed that my touchscreen wasn’t responding, so as a last step, I tried temporarily deactivating my touchscreen. The problem then went away. After a reboot, my touchscreen worked properly and the cursor no longer jumped. I have no explanation as to why, but here is how:
That will give you a list of inputs with IDs. The touchscreen entry should be pretty obvious. Mine is ‘Synaptics Large Touch Screen’. Note the ID. It should be a single or two digit number.
I do this just about every time. I don’t allocate enough drive space that my virtualbox will need. Here’s how I fixed it this time.
I have a windows development box that I allocated 40gb to as a dynamic virtual disk. I chose the “.vmdk” format, which isn’t so straight forward to expand. Had I chosen VDI or VHD, I could have used the “VBoxManage modifyhd” command, but that was a no go. I ended up with this error:
VBoxManage modifyhd windows.dev.vmdk --resize 819290
Progress state: VBOX_E_NOT_SUPPORTED
VBoxManage: error: Resize medium operation for this format is not implemented yet!
What Did Work?
I created a new virtual disk (dynamic) at the size I wanted – 80gb. This time I chose VDI. Then I ran:
You will be prompted at this point to choose between GDM and LightDM. I chose GDM at first, which I read was fine if Gnome was going to be used solely (sharks don’t look back!). I understood that LightDM is the option to choose if you are going to flip between the two. GDM caused me some graphic driver issues that left me unable to boot. I ended up in recovery and ran the above again, this time choosing LightDM. All good after that.
To get the better looking gnome login screen, run: