NoMAD crashes when a mounted share name contains spaces

Version: 1.1.0 Build: 720

NoMAD...

• ... crashes on launch if an already mounted share name contains a space. It sits on Updating User Info until the Menubar icon is clicked, at which point it throws Illegal instruction: 4.
• ... is slow to launch if there are any mounted shares. It sits on Updating User Info until the Menubar icon is clicked, at which point it proceeds normally. N.B. this only occurs on the first NoMAD launch following a share being mounted. Subsequent launches are normal, i.e. the same as if no shares are mounted.
• ... crashes if already launched and a share with a space is mounted, although the crash doesn't occur until there is some NoMAD activity.

I've verified that this behaviour occurs regardless of the credentials used to mount the shares.

NoMAD_crash_re_mounted_shares.crash

changed milestone to %V. 1.1

We'll fix this.

Please try with 1.1(721) or later.

added Ready for Testing label

Yep – the "space in name" issue is resolved in 721, thanks! However, I'm still getting the behaviour where it waits the first time I launch NoMAD following a share being mounted. Now it displays Time between system checks is too short, delaying and only continues with the AD login when I click on the menubar icon.

Also, interestingly, the first launch post-mount always triggers the password expiry notification (I only have 11 days remaining) but NoMAD launches not post-mount don't trigger this.

Interesting, please file the other issues in a new bug and we'll address them there. Thanks.