Just commited a fix for this to ubiquity's trunk that will be part of ubiquity 2.8.3.
Unfortunately I couldn't reliably reproduce this issue in a VM, so it'd be great if you could re-test with tomorrow's daily build (assuming we have ubiquity 2.8.3 on it).
Just commited a fix for this to ubiquity's trunk that will be part of ubiquity 2.8.3.
Unfortunately I couldn't reliably reproduce this issue in a VM, so it'd be great if you could re-test with tomorrow's daily build (assuming we have ubiquity 2.8.3 on it).