After an update of Skyrim Special Edition, I got the following error message attempting to run Wrye Bash:
Wrye Bash could not find a game to manage. Please use -o command line argument to specify the game path
After an update of Skyrim Special Edition, I got the following error message attempting to run Wrye Bash:
Wrye Bash could not find a game to manage. Please use -o command line argument to specify the game path
Trying to start ejabberd I got errors such as these:
2017-09-01 00:35:06.928 [error] <0.37.0> CRASH REPORT Process <0.37.0> with 0 neighbours exited with reason: {aborted,{“Cannot read schema”,”/var/lib/ejabberd/schema.DAT”,{error,{file_error,”/var/lib/ejabberd/schema.DAT”,eacces}}}} in application_master:init/4 line 133
Attempted to create a new certificate using the EasyRSA suite and got the following error:
“failed to update database”
Unfortunately the script is pretty laconic, but some quick testing showed this was due to trying to re-use the default display name:
Name [EasyRSA]:
This is a great little how-to on hiding and unhiding cells in Microsoft Excel: http://spreadsheets.about.com/od/excelformatting/qt/070814unhidecol.htm
Please excuse the mess: We’ve moved!
I got tired of my (self-hosted) wordpress site for several reasons, the main ones being:
So, I’ve migrated the Geekworker blog to blogger.com. Blogger works surprisingly well and I really like the interface. There are some drawbacks too, such as not having a good font for code snippets.
The import – I had to use a third party site for conversion – seems to have worked, too, but expect some font weirdness and broken images until I can go through all posts and fix them. Thanks for your patience!
Update, August 5th: Broken images and the worst formatting problems should now be fixed. Don’t hesitate to report problems, please!
I use OBS Studio to record videos, and would ideally like to record multiple audio tracks (so that I might balance audio levels in post-production). Unfortunately, when I import these MP4 videos into Sony Movie Studio Platinum, it detects no audio tracks.
The problem is a buggy DLL file.
To fix this, go to your program’s install folder (mine resides in D:ApplicationsSonyMovie Studio Platinum 12.0) and find a subdirectory called “FileIO Plug-Inscompoundplug”. In this folder, you will find a file called “compoundplug.dll”. Simply rename this (to “compoundplug.backup”, for example) and your Sony Vegas or Sony Movie Studio should now import mp4 files correctly – even with multiple audio tracks.
Update, 2017-08-03: Never versions of Movie Studio likely do not have this problem. I have upgraded to Vegas Pro 14, and it reads files with multiple audio tracks just fine.
I use Livestreamer to download my own VOD files when I dun goofed and break my local recordings. This used to work perfectly, but as I write this, the software is broken due to an update in the Twitch API that enforces authentication.
error: Unable to open URL:
https://api.twitch.tv/api/channels/havejoystick/access_token.json
(400 Client Error: Bad Request)
There is a workaround, however; you can hand over a client specific token. Right now, this is the one used by Twitch’s web player:
livestreamer --http-header Client-ID=jzkbprff40iqj646a697cyrvl0zt2m6
This works like a charm. For now.
While setting up a new OpenVPN, I got this message:
Sep 23 21:05:25 ascalon openvpn[18770]: krynn/aaa.bbb.ccc.ddd:xxxxx IP packet with unknown IP version=3 seen
The cause was that I had set my OpenVPN server to “dev tun”, while setting my Windows client to “dev tap” in the configuration. Changing the client to also be “dev tun” fixed the issue.
I’m currently setting up a new server and ran into something odd. Connecting to ejabberd with Pidgin, the later would reject the SSL certificate outright. At first I thought I had messed up the hostnames, or used an outdated Hash algorithm or whatever.
The errors I saw in the debug window were:
(22:17:42) nss: ERROR -8102: SEC_ERROR_INADEQUATE_KEY_USAGE
(22:17:42) nss: ERROR -8101: SEC_ERROR_INADEQUATE_CERT_TYPE
It turns out that SSL certificates can be flagged for what they can be used for, and I had simply created the certificate with the ./build-key command. Using ./build-key-server instead fixes the issue. The difference is that this will set nsCertType=server in the certificate.
I hope this helps anybody who runs into the same issue – it certainly had me pulling out my hair for a while.