I first posted about this in 2019, running 10.13 on a 2009 iMac. I had
hoped this bug would be fixed by now in Big Sur but it hasn't.
Spouse and I use two different user accounts on the same Mac. We share
the same Photos library, stored on an external drive with ownership
ignored.
Starting in 10.13, quitting Photos doesn't stop the photolibraryd
process. That means that if one of us had been using (and quit) Photos,
the other can't open the libray because it's "on a locked disk", but the probem really is the other user's photolibraryd process that is still running. We have to log the other user out, or force quit the
photolibraryd process.
Also, even if force quit, photolibraryd seems to start up again randomly
on its own, even if Photos is not launched.
Any way to make this process go away when quitting Photos, and make it
stay away? What is it doing anyway when Photos isn't even running?
I first posted about this in 2019, running 10.13 on a 2009 iMac. I had
hoped this bug would be fixed by now in Big Sur but it hasn't.
Spouse and I use two different user accounts on the same Mac. We share
the same Photos library, stored on an external drive with ownership
ignored.
Starting in 10.13, quitting Photos doesn't stop the photolibraryd
process. That means that if one of us had been using (and quit) Photos,
the other can't open the libray because it's "on a locked disk", but the probem really is the other user's photolibraryd process that is still running. We have to log the other user out, or force quit the
photolibraryd process.
Also, even if force quit, photolibraryd seems to start up again randomly
on its own, even if Photos is not launched.
Any way to make this process go away when quitting Photos, and make it
stay away? What is it doing anyway when Photos isn't even running?
Sysop: | Gate Keeper |
---|---|
Location: | Shelby, NC |
Users: | 790 |
Nodes: | 20 (0 / 20) |
Uptime: | 41:45:01 |
Calls: | 12,115 |
Files: | 5,294 |
Messages: | 564,934 |