SUMMARY After saving a picture, keyboard becomes unresponsive until something is done with the mouse STEPS TO REPRODUCE 1. In digikam main window, in an album select several or all pictures (using Ctrl-A for instance) (3 or more) 2. Open the Image Editor with the Image Editor button 3. Do a trivial change on the image shown (for instance, rotate it right using Ctrl-Shift-Right) 4. Press cursor right key to move on to second image 5. Save dialog pops up, as it should. Confirm saving by pressing Space 6. Press cursor right key again to move on to third picture OBSERVED RESULT Nothing happens. Or rather, keyboard is just ignored in general until something is done with mouse (a click, or moving it out and back into window). EXPECTED RESULT The Image Editor should move on to third picture SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian 11 (available in About System) KDE Plasma Version: 5.20.5-1 KDE Frameworks Version: 5.78.0-2 Qt Version: 5.15.2 ADDITIONAL INFORMATION Bug is annoying when attempting to changes to lots of images with keyboard shortcuts
Please test it with a more recent version, e.g. with the AppImage from here: https://files.kde.org/digikam/ However, make a backup of the databases if you want to go back to your old version. Maik
You are working with a 2 year old digiKam version. In the meantime, hundreds of bugs have been fixed and improvements made. Maik
(In reply to Maik Qualmann from comment #1) > Please test it with a more recent version, e.g. with the AppImage from here: > > https://files.kde.org/digikam/ > > However, make a backup of the databases if you want to go back to your old > version. > > Maik Unfortunately, the problem still occurs with the AppImage version :-(
(In reply to Maik Qualmann from comment #2) > You are working with a 2 year old digiKam version. I'm working with the version that is included in the currently stable Debian version. > In the meantime, hundreds > of bugs have been fixed and improvements made. Good to know, but unfortunately this one is not among them :-( (see my previous comment) > > Maik Alain
I can't reproduce the problem, maybe the focus is not returned to digiKam by the window manager after the save dialog. Are you using Wayland or X11 and which window manager? Maik
(In reply to Maik Qualmann from comment #5) > I can't reproduce the problem, maybe the focus is not returned to digiKam by > the window manager after the save dialog. Are you using Wayland or X11 and > which window manager? > > Maik I'm using X11, with KDE and its window manager kwin Why would the window manager screw up focus? It doesn't do this with other applications in similar circumstances. But if you suspect a bug in kwin, please explain why you think it might be a kwin issue, and I'm ready to report it there. I did notice though that just moving the mouse out of and back into the window seems to address the issue (but that workaround is still cumbersome, but might point us into the right direction)
With Plasma desktop this problem can be also relevant of the OpenGL effect turned on in the desktop settings. Try to disable the Plasma desktop effects and try again. Gilles Caulier
(In reply to caulier.gilles from comment #7) > With Plasma desktop this problem can be also relevant of the OpenGL effect > turned on in the desktop settings. > > Try to disable the Plasma desktop effects and try again. > > Gilles Caulier I do not have "Desktop settings", but I do have settings for "Desktop effects". This lists numerous effects, but none of them is called plasma. Or do you mean to switch off *all* desktop effects, no matter their name? In "Compositor", I have "Rendering Backend", which can be set to "OpenGL 3.1", "OpenGL 2" or "XRender". It already was XRender. So, *exact* names / spellings of settings to change would definitely help me test this out. In any case, this still looks like a bug to be, other applications do pop up dialogs on occasion too, but this problem does not happen to them. So digikam must be doing something weird here, that no other application does, even if it does break by confusing kwin.
I had a look at the save confirmation window using xprop, and I noticed that it had its WM_TRANSIENT_FOR property set pointing to digikam's *main* window, rather than to the ImageEditor window. Could that be what is confusing kwin? WM_TRANSIENT_FOR(WINDOW): window id # 0x4e0001f
@Alain, digiKam 8.0.0 is out. This entry still valid with this release ? Best regards Gilles Caulier
Problem still occurs with version 7.9.0 as included in Debian 12
Alain, What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Thanks in advance Gilles Caulier