cool, thanks for that.
I wonder though, if the “Locations — System Settings” routine is supposed to be for creating any location you want for Desktop, Documents, Downloads, Videos, Pictures and Music, then why doesn’t it retain the data I type into those fields and apply them? I read the link and I didn’t see an explanation. I think what’s happening is that the drives are being mounted after the custom directories are being read, and if so then I see it as unexpected behavior unless that is on some to-do list to put those actions in the right order: 1) mount drives 2) check for the existence specified folder locations otherwise default them.
What’s your theory on the issue from the perspective of expected behavior of the “locations system services” paths dialog? Can I still use the beautiful “locations — system settings” dialog window if I zero the sdg-user-dirs-update bool? If this is “just the way Manjaro is” then perhaps there can be a note that says you can’t use custom paths that are on another drive than the system one, which does seem weird.
I think “mount drives at login” isn’t soon enough. I suspect that the directories are already made before login has happened. What needs to happen is that drives need to be mounted before KDE is spawned for KDE to find the folders in other drives. That’s at least my theory.
but maybe it’s a security issue. if so, then there needs to be a delay after login and drive auto-mounts, and then run the bit of code that checks if paths exist after a few hundred milliseconds has elapsed.