You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During an operation with the program, a dialog box tells you the progress and allows you to cancel at anytime.
But the operation keeps rolling until the end even if you press cancel. This becomes an issue for huge batch of files, forcing you to close if from a program manager.
This seems to have something to do with qdbus and the wasCancelled but I could not find any report on the command set.
Replacing "qdbus", by qdbus6 or qdbus-qt5 didn't work.
Ok, found the reason (a really stupid one at that).
The program uses qdbus to see if the "Cancel" button has been pushed.
But there's a quirk with kdialog where the "Cancel" button also closes the dialog, thus destroying the dbus reference needed by the abort logic.
KDE/ kdialog seems to be more at fault for not letting the programs manage the qdbus by themselves, but instead "baby-holding" them.
During an operation with the program, a dialog box tells you the progress and allows you to cancel at anytime.
But the operation keeps rolling until the end even if you press cancel. This becomes an issue for huge batch of files, forcing you to close if from a program manager.
This seems to have something to do withqdbus
and thewasCancelled
but I could not find any report on the command set.Replacing "qdbus", by qdbus6 or qdbus-qt5 didn't work.
Ok, found the reason (a really stupid one at that).
The program uses qdbus to see if the "Cancel" button has been pushed.
But there's a quirk with kdialog where the "Cancel" button also closes the dialog, thus destroying the dbus reference needed by the abort logic.
KDE/ kdialog seems to be more at fault for not letting the programs manage the qdbus by themselves, but instead "baby-holding" them.
Tested with:
EndeavourOS, Plasma 6.2, Wayland / X11
Kubuntu 24.04, Plasma 5.27, X11
The text was updated successfully, but these errors were encountered: