Sadly, this isn't a Canonical thing (Canonical only manages the main repository, this package is in the universe repository which is community supported). Furthermore, this was auto-sync'd from Debian, which means it's an upstream issue, but I couldn't find a matching upstream bug.
I might be taking on this bug if reverting the changes in the -1.1 done upstream in Debian do the trick. Otherwise, reverting to 3.7.2 is a bigger task.
Sadly, this isn't a Canonical thing (Canonical only manages the main repository, this package is in the universe repository which is community supported). Furthermore, this was auto-sync'd from Debian, which means it's an upstream issue, but I couldn't find a matching upstream bug.
I might be taking on this bug if reverting the changes in the -1.1 done upstream in Debian do the trick. Otherwise, reverting to 3.7.2 is a bigger task.