Bug #12360

Florence indicator state can get out-of-sync with Florence status

Added by anonym 2017-03-17 17:01:49 . Updated 2017-09-28 18:50:17 .

Status:
Resolved
Priority:
Low
Assignee:
Category:
Target version:
Start date:
2017-03-17
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
On-screen keyboard
Deliverable for:

Description

This is quite easily reproducible by:

  • Booting Tails and logging in
  • As soon as the Desktop is shown, when the session is still starting up, spam click on the Florence indicator (a single double-click can be enough, fwiw)
  • The result is: Florence is shown, but clicking on the indicator doesn’t hide it, it only changes the indicator’s state from now on

Note that the “when the session is still starting up” part seems necessary — I cannot reproduce this in a session where everything has started and calmed down.


Subtasks


History

#1 Updated by intrigeri 2017-03-21 08:46:47

I’m not surprised this works poorly given the way the _toggle function is implemented (with hard-coded time interval) in the florenceIndicator GNOME Shell extension.

#2 Updated by intrigeri 2017-05-27 08:38:52

  • Target version changed from Tails_3.0 to Tails_3.1

I don’t think anyone will have time to work on this during the 3.0 cycle.

#3 Updated by intrigeri 2017-06-28 16:57:27

  • Target version deleted (Tails_3.1)
  • Type of work changed from Research to Code

Nobody reported this since the 3.0 release, so at the help desk / foundations team meeting today, we deemed this ticket as low priority.

#4 Updated by Anonymous 2017-06-29 12:13:46

  • Priority changed from Normal to Low

lowering priority.

#5 Updated by intrigeri 2017-07-25 07:38:39

  • Affected tool set to On-screen keyboard

#6 Updated by intrigeri 2017-09-15 17:45:43

  • Status changed from Confirmed to Fix committed
  • Target version set to Tails_3.2

We don’t ship Florence anymore (Feature #8281) and the GNOME on-screen keyboard has no such bug.

#7 Updated by anonym 2017-09-28 18:50:17

  • Status changed from Fix committed to Resolved