Comment 3 for bug 1963276

@alecos85: "No solution" is not true. That bug has been closed by the reporter that upgrading qutebrowser to a more recent version has solved the issue. (Although I suspect that actually an Qt upgrade in the same timeframe was the real reason for this being fixed. See upstream's comment in that bug report.)

Hint: Don't rely on external mailing list archives when reading Debian bug reports. Read the bug report in Debian's Bug Tracking System directly: https://bugs.debian.org/960384