Looks like this was already fixed in 1.0.7-1 a couple of weeks ago. I
updated and the problem went away. Sorry for the dupe.

Reply via email to