This issue has been fixed upstream in version 1.2.18.0:

  http://mlmmj.org/hg/mlmmj/rev/f7295507141c

So IMHO this bug can be closed.

-- 
Ramiro

Reply via email to