SUMMARY Can't re-save k3b project file. STEPS TO REPRODUCE 1. Start k3b. 2. File->New Project->New Audio CD Project 3. Drop a file into the project. 4. File->Save as... 5. Save as /tmp/abc. The file dialog will add the .k3b extension. 6. Having made no further changes, press Ctl+S to save again. OBSERVED RESULT k3b pops up the "File Already Exists" dialog, which looks normal, bur somehow doesn't have the focus. You can't change the file name, or click on any of the buttons. No combination of tab, typing or clicking the mouse can use or dismiss this dialog box, and you have to forcibly kill k3b (thus losing any changes you made) to get out. EXPECTED RESULT k3b saves the file w/o prompting or hanging. SOFTWARE/OS VERSIONS KDE Frameworks Version: KDE Frameworks 5.82.0 Qt Version: Qt 5.15.2 (built against 5.15.2) Related to, but different than, bug 392617.
Forgot to add - a k3b :Progress Dialog" also pops up - similarly unresponsive to mouse clicks. Screenshot attached.
Created attachment 138716 [details] Screenshot
A possibly relevant merge request was started @ https://invent.kde.org/multimedia/k3b/-/merge_requests/10
possibly bug 392617 is a duplicate.
Patrick - I mentioned that one in the original bug submission. I think they're related, but not the same bug.
Git commit 2a4b66e3a417559599d3bc61ce6497e17ec98472 by Albert Astals Cid. Committed on 24/05/2021 at 09:57. Pushed by aacid into branch 'release/21.04'. Fix showing of dialog the user can't interact with when saving The issue is using KIO::move + exec() can show a dialog but exec says to QEventLoop::ExcludeUserInputEvents so the user is stuck there forever. Move to KIO::file_move since we're moving files anyway and set overwrite since we're already asking if the file exists anyway (twice in fact, fix coming in the next commit) M +2 -2 src/k3bprojectmanager.cpp https://invent.kde.org/multimedia/k3b/commit/2a4b66e3a417559599d3bc61ce6497e17ec98472
I can't reproduce my bug after this fix. Thank you Albert.
*** Bug 392617 has been marked as a duplicate of this bug. ***
Thank you for the fix!
*** Bug 444729 has been marked as a duplicate of this bug. ***