As kde4libs are not in Bullseye anymore and phased out completely, we have moved to the KDE Frameworks generation of technology.
This defect is potentially not relevant anymore as a lot of the technology is different now. At least it needs a new reproduction and thus confirmation that is is still present on Bullseye or Unstable/ Testing. My suggestion is to close the report, because there would have been more information meanwhile if a similar defect has shown in the last 9 years. Leslie thanks again for reporting this problem, sorry that it could not fixed for kde4libs based technology. (Or, by chance are you still using the new stuff and experiencing still such problems?)
