Steam won't start on my Mac!

 Sometime in the recent past year, Steam stopped working, and 'reinstalling' didn't work.  So I finally investigated it today.  I opened Console, launched the app, and then searched for 'steam' in the console log entries.  I found this:

Unsupported 32-bit executable: "/Users/USERNAME/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/steam_osx"

Ok... but I deleted the app and reinstalled??

So I pulled up terminal, and went to  /Users/USERNAME/Library/Application Support/Steam/  and found that most of the files in this folder were dated 2018.  :-/

Renamed /Users/USERNAME/Library/Application Support/Steam/ to /Users/USERNAME/Library/Application Support/Steam.old

Relaunch Steam and this time it started to download the latest update...   OK good, now let's try redoing this with just renaming the Steam.AppBundle folder instead...

A couple of runs (update downloads, then update runs, then actually starting) and it worked.

Make 1Password work with Google Canary

https://support.1password.com/kb/201707/

# cp ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/2bua8c4s2c.com.agilebits.1password.json ~/Library/Application\ Support/Google/Chrome\ Canary/NativeMessagingHosts/

Restart Canary

Ubuntu: Totem: "Could not initialize support library"

Running totem from command line told me the following excerpt:

VA-API version 0.39.0
Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
va_openDriver() returns -1

That's a sign you don't have VAAPI support in your video card driver.  In my case, I have an ATI Radeon card  which support VDPAU.

The answer is to remove the gstreamer vaapi package:

# sudo apt-get remove gstreamer1.0-vaapi

DNS Name lookup (was SSH) Not Working After Snow Leopard Upgrade - Server Fault

DNS Name lookup (was SSH) Not Working After Snow Leopard Upgrade - Server Fault: sudo killall -USR1 mDNSResponder

Fix for broken search domain resolution in OS X Yosemite | Computero

Fix for broken search domain resolution in OS X Yosemite | Computero



Very recently my Yosemite 10.10.4 machine stopped being able to resolve short hostnames for local systems on my personal network when using ping or ssh, but working fine for dig and nslookup.  There are countless threads about discoveryd being the culprit, and indeed it is.   Unloading and loading it wasn't helping.  I finally found the above link, and quite frankly it doesn't make any good sense why it should work, but it did fix my problem.  My local DNS is running a dnsmasq, answering both pre-defined hostnames and forwarding the remainder to my ISP's DNS servers, so the 'search' entry in /etc/resolv.conf is automatically being populated with my ISP's xyz.rr.com.  This has never been an issue before, and honestly I don't think even should be attempted unless the short name lookup fails, but whatever.



Annoyed but happy I fixed it.

Fluid - Turn Your Favorite Web Apps into Real Mac Apps.

Fluid - Turn Your Favorite Web Apps into Real Mac Apps.:



'via Blog this'

Aperture import plugin now available

Aperture import plugin now available:



'via Blog this'

retina macbook pro - Stop Chrome from switching to dedicated GPU - Ask Different

retina macbook pro - Stop Chrome from switching to dedicated GPU - Ask Different:



'via Blog this'

Samiux's Blog: HOWTO : ECS LIVA Mini PC Kit on Ubuntu 14.04 LTS

Samiux's Blog: HOWTO : ECS LIVA Mini PC Kit on Ubuntu 14.04 LTS:



'via Blog this'

Saving Onkyo TX-NR5008 settings - Tom Gutwin

Saving Onkyo TX-NR5008 settings - Tom Gutwin