Tim's Weblog » error

Hyves kan…

Tim — Fri, 09 Apr 2010 20:31:56 +0000

Hoe raadt ie het zo!?!?!

[crypto] OpenSC seems to break GnuPG?

Tim — Thu, 27 Aug 2009 13:17:08 +0000

So, I’ve been trying to get a SCM SPR532 working yesterday, but that didn’t really want to play nice. Today, I wanted to use my trusty old SCM SCR335 again, but GnuPG kept giving me sharing violations like so:

$ gpg -d secretdocument.gpg
gpg: detected reader `SCM SCR 335 00 00'
gpg: pcsc_connect failed: sharing violation (0x8010000b)
gpg: kaartlezer is niet beschikbaar

(The last line read “card reader not available” in Dutch.)

Very annoying. I tried shooting down the running pcscd, but that didn’t help. Then, I uninstalled OpenSC, which seemed to have helped. No idea why, but honestly, the documentation is so very vague, I hardly know how all these components work together.

Anyway, I hope it helps someone.

Tags: crypto, encryption, error, gnupg, opensc, pcscd, scm, scr335, spr532, troubleshooting

Firefox: ASSERT: *** Search: _installLocation: engine has no file!

Tim — Tue, 07 Apr 2009 16:00:04 +0000

So if you get the above error, you probably upgraded your Firefox and forgot to restart it. A customer of ours ran into that and it took me a little while to figure out the problem wasn’t with our server, but with his Firefox. Silly message, anyway. But I guess that’s what programmers are good at, confronting their users with silly messages that are unusable if you’re not programming on the application you’re using.

Tags: error, firefox

Darcs failed: problem gzwriting file

Tim — Mon, 06 Apr 2009 12:17:13 +0000

I got this error from a darcs installed on Etch:

tim@machine:/etc$ darcs record -am 'Initial checkin'

darcs failed: problem gzwriting file: _darcs/patches/20090406120803-59231-78a2a82198e9134e0cf5600d03958044b779cc47.gz-0 tim@machine:/etc$

Google didn’t turn up anything, so I used strace as a last resort. That quickly pointed out the problem, darcs couldn’t read one of the files I tried to add. If you use strace, scroll up a bit and look for something like this:

open("/etc/postgresql/8.1/main/pg_ident.conf", O_RDONLY|O_NONBLOCK|O_NOCTTY) = -1 EACCES (Permission denied)

That’s the file I either needed to remove from the record or add to boring (and remove it from the pending file). Or make readable.

Hope this helps someone.

Tags: darcs, error, failed, gzwriting, permissions, strace, work

MySQL says: “ERROR 1030 (HY000): Got error -1 from storage engine”

Tim — Mon, 08 Dec 2008 01:04:28 +0000

In my case, this meant it was not allowed to write data (an INSERT) to a InnoDB table because innodb_force_recovery was set too high. Took me a while to figure out, so I hope this helps someone.

Solution is to simply disable the innodb_force_recovery. You should use that setting only for making an emergency dump anyway.

More about my wanderings through MySQL+InnoDB+NFS land soon.

Tags: error, innodb, mysql, vague

Fixing X11 on Mac OS X 10.4 (Tiger)

Tim — Mon, 06 Oct 2008 13:49:39 +0000

I had some trouble getting X11.app to work. No idea why it stopped working all of a sudden, I don’t think I did anything strange that might break it. I got:

idefisk:/Applications/Utilities tim$ ./X11.app/Contents/MacOS/X11

XFree86 Version 4.4.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) [DRI] screen 0 installation complete Screen 0 added: 1280x800 @ (0,0) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! exec: No such file or directory Quitting XDarwin... idefisk:/Applications/Utilities tim$

While researching this, I came across this page describing how to make Tiger’s X11 work on Leopard. It included the following step:

The final step is to edit the file /etc/X11/xinit/xinitrc and go to the bottom of the file and replace "exec quartz-wm" with "exec /usr/X11R6/bin/quartz-wm".

Well, my Tiger didn’t even have an /etc/X11/xinit directory. So I created it and added the xinitrc file with that one line. Now my X11.app works again. Yay!

Hope this helps someone else.

Update: Fixed the title. Tiger is of course 10.4, not 10.5.

Tags: error, macosx, starting, tiger, x11, x11.app