在 2021-07-20星期二的 13:16 -0500，allan写道： > This has only been broken for a couple of days - there's a strong > possibility that whatever broke it hasn't made it to Bullseye yet. > This appears to be an upstream bug because a Manjaro user running same > version of flameshot and Qt is experiencing same behavior and as > mentioned, it broke a couple of days ago.
This is exactly the merit of release freeze -- anyway, you may check what has been updated in unstable in the past few days. Please let me know if you have any findings. As the packager, I would be targeting on flameshot 0.10.0 when the freeze is over and it would be meaningful if we could analyze whether it's still broken with new release then. Thanks, Boyuan Yang > On Tue, Jul 20, 2021 at 11:54 AM Dennis Filder <d.fil...@web.de> wrote: > > > > X-Debbugs-CC: allan grossman <wizard10...@gmail.com> > > > > I can't reproduce this under current Bullseye KDE/xorg -- flameshot > > behaves absolutley normally. It could be a Wayland issue, and > > flameshot's Wayland support is apparently still experimental. > > > > Let us know if running flameshot like so fixes this for you: > > > > GDK_BACKEND=x11 flameshot > > > > Regards, > > Dennis Filder
signature.asc
Description: This is a digitally signed message part
