is this a known bug that collections marked as removable can become local?
I decided to make a symlink in /Photos to a removable media link, and marked it as being on removable media. But after some reboot, logout or new instance of digikam , it decided this album was going to on local media. This is bad for me. The next thing that happens is that it got removed, and now it has to rebuild the whole database data, which takes forever in my case, perhaps 100k images. I'm going to try and re-mark them, otherwise I run the risk again that when I forget to mount that drive and I start digikam, it's game over again. Could also cheat and use sqlitebrowser to edit the "type" field in the AlbumRoots. Isn't this a bug to change its mind on what's Local and Removable??? - peter |
Yes, we have an older bug report. We use the KF5 Solid API for these things.
With a symlink, I could imagine that Solid would then see a local file system instead of the removable medium. Maik Am Samstag, 23. Mai 2020, 05:40:54 CEST schrieb Peter Teuben: > is this a known bug that collections marked as removable can become local? > > > I decided to make a symlink in /Photos to a removable media link, and > marked it as being on removable media. > > But after some reboot, logout or new instance of digikam , it decided > this album was going to on local media. This is bad for me. The next > thing that happens is that it got removed, and now it has to rebuild the > whole database data, which takes forever in my case, perhaps 100k images. > > I'm going to try and re-mark them, otherwise I run the risk again that > when I forget to mount that drive and I start digikam, it's game over > again. Could also cheat and use sqlitebrowser to edit the "type" field > in the AlbumRoots. > > Isn't this a bug to change its mind on what's Local and Removable??? > > - peter |
Maik
I had a casual search for a bug, but didn't see it, so i rushed to posting here. I was able to hack the database and flip the type of the album. Just have to be careful when I reboot next time. peter On 5/23/20 12:28 AM, Maik Qualmann wrote: > Yes, we have an older bug report. We use the KF5 Solid API for these things. > With a symlink, I could imagine that Solid would then see a local file system > instead of the removable medium. > > Maik > > Am Samstag, 23. Mai 2020, 05:40:54 CEST schrieb Peter Teuben: >> is this a known bug that collections marked as removable can become local? >> >> >> I decided to make a symlink in /Photos to a removable media link, and >> marked it as being on removable media. >> >> But after some reboot, logout or new instance of digikam , it decided >> this album was going to on local media. This is bad for me. The next >> thing that happens is that it got removed, and now it has to rebuild the >> whole database data, which takes forever in my case, perhaps 100k images. >> >> I'm going to try and re-mark them, otherwise I run the risk again that >> when I forget to mount that drive and I start digikam, it's game over >> again. Could also cheat and use sqlitebrowser to edit the "type" field >> in the AlbumRoots. >> >> Isn't this a bug to change its mind on what's Local and Removable??? >> >> - peter > > > |
Free forum by Nabble | Edit this page |