This is still an issue with the 0.4.13-1 upgrade. I'm downgrading once again to 
0.4.11-5 until the issue gets resolved or a proper workaround is provided, 
preferrably via apt-listchanges News.

Reply via email to