I'm currently using a 64-bit system, sadly.I've just had the problem occur on Debian Testing (AMD-64), so it looks like the problem is simply more prevalent on Trisquel, for some reason.
Annoyingly, there doesn't seem to be anything mentioned in the logs.
