It seems that the Home Folder launcher cannot execute properly if its parent process is started too early on in your session. Starting Do after your session has started appears to fix this problem, so this is not a Do bug. We may try to prevent this quirky behavior by adding an artificial delay to our session startup.
It seems that the Home Folder launcher cannot execute properly if its parent process is started too early on in your session. Starting Do after your session has started appears to fix this problem, so this is not a Do bug. We may try to prevent this quirky behavior by adding an artificial delay to our session startup.