>> So this bug is possibly fixed with Qt5 5.15.6+dfsg-4, to be confirmed by>> 
>> you and others when you have the opportunity to upgrade Qt (libqt5*>> 
>> packages).
> Then let's close this bug. Thanks for checking.
>
> Cheers>
>Sebastian Ramacher

I really don't understand your logic for closing this bug, can you explain it? 
Do you have a patch for this bug? Have you tested it and found that it resolves 
the issue?

I'm the person who opened this bug and the issue is still present for me in 
Bookworm.

Regards,

Reply via email to