Bug 495372 - After match-by-hash, browser view is not fully consistent
Summary: After match-by-hash, browser view is not fully consistent
Status: CONFIRMED
Alias: None
Product: kphotoalbum
Classification: Applications
Component: Browser (show other bugs)
Version: 5.13.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KPhotoAlbum Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-26 10:02 UTC by Pierre Etchemaïté
Modified: 2024-11-01 18:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Failure to access files after update-by-hash partial update (1.05 MB, image/jpeg)
2024-10-26 10:02 UTC, Pierre Etchemaïté
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre Etchemaïté 2024-10-26 10:02:02 UTC
Created attachment 175252 [details]
Failure to access files after update-by-hash partial update

SUMMARY

After renaming image files, "refreshing" the database updates the names shown in the browser, but the image paths are not updated. Also, operation "put on top of stack" on those images fails, I can't tell if that's because of wrong path or reveals other internal inconsistencies. Saving and restarting kPhotoAlbum fixes the inconsistencies. 

STEPS TO REPRODUCE
1. display the thumbnails of some images
2. (recalculate their hashes to make sure hashes are up-to-date)
3. rename the files in filesystem
4. refresh the kPhotoAlbum database
5. wait for the displayed names to be updated
6. try some operation that involves access to the files (recalculate hashes again, display in full,...)

OBSERVED RESULT

kPhotoAlbum browser tries to open non-updated file paths, and fails.

EXPECTED RESULT

All the information about the files should be updated by the refresh operation, in both database and browser.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux Ubuntu 22.04.5 LTS
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Comment 1 Johannes Zarl-Zierl 2024-11-01 18:18:55 UTC
Thanks for reporting this bug.

I could reproduce this using the demo database. It seems to be a problem with updating the view, since the problem goes away if one browses to a different view and comes back to the same thumbnail view.