> I confirm this. The solution is to upgrade your liboctave1 package to > version 3.6.3-2. Thanks for the tip; I would have upgraded that at the same time, but managed to overlook it since it's a long way away in an alphabetical list. That does indeed fix it.