Comment 3 for bug 1668744

Revision history for this message
Erno Kuusela (erno-iki) wrote :

I reported it upstream and the author replied that it has already been fixed in the latest version, apparently there has been a rewrite of the command line handling. It didn't seem like there was going to be a security advisory on his part or anything.

What's the right way to getting this fixed in Ubuntu?