[Bug]: Soft Lock After Scan #114

Closed
opened 2026-06-21 23:15:56 +00:00 by ValleyGeek · 1 comment
Owner

App version

0.1.54 Beta

Platform

Windows

Steps to reproduce

  1. Open a directory
  2. Allow the initial scan to run

Expected behavior

The UI shouldn't lock during the process but if it must, there needs to be something displayed to the user noting what's happening with a progress indicator.

Actual behavior

After the count for "Indexing" is completed and before "Scan Complete" is displayed, an action is locking the UI but not giving the user any feedback that something is happening.

Additional context

No response

### App version 0.1.54 Beta ### Platform Windows ### Steps to reproduce 1. Open a directory 2. Allow the initial scan to run ### Expected behavior The UI shouldn't lock during the process but if it must, there needs to be something displayed to the user noting what's happening with a progress indicator. ### Actual behavior After the count for "Indexing" is completed and before "Scan Complete" is displayed, an action is locking the UI but not giving the user any feedback that something is happening. ### Additional context _No response_
Member

Root cause: _on_deep_finished (main_window.py) runs several synchronous main-thread steps after the scan worker's finished signal fires — recent-dir bookkeeping, dupe-tag-singleton pruning, and (when the workspace lives on a network share) a silent cache copy — before the status bar updates to "Scan complete." None of that work emitted any progress feedback, so the UI appeared to lock between the end of "Indexing" and the completion message.

Fix (branch 0.2.2/issue-114-soft-lock-after-scan): show a "Finalizing scan..." status message with a busy progress indicator as soon as the scan finishes and before this cleanup runs, and route the network-share sync through the existing progress-UI path instead of running it silently. Work continues on the branch; PR to main pending user request.

Root cause: `_on_deep_finished` (main_window.py) runs several synchronous main-thread steps after the scan worker's `finished` signal fires — recent-dir bookkeeping, dupe-tag-singleton pruning, and (when the workspace lives on a network share) a silent cache copy — before the status bar updates to "Scan complete." None of that work emitted any progress feedback, so the UI appeared to lock between the end of "Indexing" and the completion message. Fix (branch `0.2.2/issue-114-soft-lock-after-scan`): show a "Finalizing scan..." status message with a busy progress indicator as soon as the scan finishes and before this cleanup runs, and route the network-share sync through the existing progress-UI path instead of running it silently. Work continues on the branch; PR to `main` pending user request.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ai-collab/bulk-image-organizer#114
No description provided.