Your message dated Tue, 09 Apr 2024 07:56:59 +0200
with message-id <46c0d737040d5b20476ac05ff1ebd...@phys.ethz.ch>
and subject line keyboard shortcuts
has caused the Debian Bug report #999472,
regarding Flowblade 2.6 keyboard shortcuts don't work in bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
999472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flowblade
Version: 2.6-3
Tags: bullseye,fixed-upstream,fixed-in-experimental
Installing flowblade in bullseye from the repositories yields a user
interface in which the keyboard shortcuts don't work. As these shortcuts
are rather essential to an efficient flowblade workflow, this bug renders
flowblade prohibitively inefficient.
The same bug has been reported upstream against the same flowblade version
in January:
https://github.com/jliljebl/flowblade/issues/984
At the time, the developer dismissed it as a problem with GTK 3.24 :
https://github.com/jliljebl/flowblade/issues/984#issuecomment-770203957-permalink
However, on my systems (running bullseye), the issue was resolved by
installing the (deb package) version 2.8.0.2-1 that is recommended by the
developer (at the time of writing):
https://github.com/jliljebl/flowblade/releases/download/v2.8.0.2/flowblade-2.8.0.2-1_all.deb
Also unaffected is the (slightly newer) version 2.8.0.3-3 in the testing
(bookworm) repository.
This leads me to speculate that the developer eventually concluded that
the alleged GTK issue wasn't going away and implemented a workaroud/fix in
flowblade 2.8 .
Detail: I triggered this bug in mate-desktop-environment . However, the
upstream report suggests that the bug will occur in other (GTK-based?)
desktop environments as well:
https://github.com/jliljebl/flowblade/issues/984#issuecomment-770199714-permalink
--- End Message ---
--- Begin Message ---
Hi Kenno
Thanks for the report, but this appears fixed upstream.
If you feel this is still a problem, feel free to re-open.
Best,
Alex
--- End Message ---
