Bug #13469

Starting applications "via GNOME Activities Overview" step is fragile

Added by bertagaz 2017-07-14 10:17:27 . Updated 2019-09-12 16:14:15 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Test suite
Target version:
Start date:
2017-07-14
Due date:
% Done:

100%

Feature Branch:
https://salsa.debian.org/tails-team/tails/merge_requests/37#note_108671
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Test suite fails with:

FindFailed: can not find GnomeActivitiesOverview.png

Happened 14 times in June 2017, 21 for what logs we have.

It does open the Gnome applications menu though, as shown by the screenshot.

Maybe the SUPER key press is lost, or we have to bump a bit the waiting time for the Gnome activities overview panel to be displayed?


Files


Subtasks


Related issues

Related to Tails - Feature #12289: Deal with June 2017 false positive scenarios Resolved 2017-06-05 2017-07-05
Related to Tails - Bug #11401: robust_notification_wait sometimes opens the Applications menu which breaks tests Resolved 2016-05-05
Related to Tails - Feature #12652: Improve the 'I start ... via GNOME Activities Overview' step Confirmed 2017-06-07

History

#1 Updated by bertagaz 2017-07-14 10:17:51

  • related to Feature #12289: Deal with June 2017 false positive scenarios added

#2 Updated by bertagaz 2017-07-14 10:18:20

  • Priority changed from Normal to Elevated

Bumping priority, it’s concerning all scenarios.

#3 Updated by intrigeri 2017-07-17 15:13:11

  • Assignee set to bertagaz
  • QA Check set to Info Needed

bertagaz wrote:
> It does open the Gnome applications menu though, as shown by the screenshot.

And that’s precisely why the Overview does not open: the SUPER key is ignored when the Applications menu is open.

> Maybe the SUPER key press is lost, or we have to bump a bit the waiting time for the Gnome activities overview panel to be displayed?

… so I believe neither of these will work.

Last time we had a similar issue (Bug #11401), it was caused by one of our hacks that clicked in the wrong place and opened the Applications menu as a result. I suspect it’s the same here. Can you please attach the debug log and video?

#4 Updated by intrigeri 2017-07-17 15:13:22

  • related to Bug #11401: robust_notification_wait sometimes opens the Applications menu which breaks tests added

#5 Updated by intrigeri 2018-09-18 06:39:22

  • Assignee deleted (bertagaz)
  • QA Check deleted (Info Needed)

I’ve noticed another source of fragility here: sometimes the Overview opens just fine, we type our query (in my case, “Disks”) but there’s no search results. Looking at the Journal, I notice that starting to type a search query in the Overview triggers the startup of a number of DBus services (org.gnome.ControlCenter.SearchProvider, org.gnome.Nautilus, org.gnome.Calculator.SearchProvider, org.gnome.seahorse.Application). It looks like there’s a bug in GNOME Shell here.

> Can you please attach the debug log and video?

One year later, I’m giving up.

#6 Updated by intrigeri 2018-09-18 14:42:17

intrigeri wrote:
> I’ve noticed another source of fragility here: sometimes the Overview opens just fine, we type our query (in my case, “Disks”) but there’s no search results. Looking at the Journal, I notice that starting to type a search query in the Overview triggers the startup of a number of DBus services (org.gnome.ControlCenter.SearchProvider, org.gnome.Nautilus, org.gnome.Calculator.SearchProvider, org.gnome.seahorse.Application). It looks like there’s a bug in GNOME Shell here.

I’ve implemented a workaround for this problem (a1d045bd167e47d620d6c2b22259bf6a946e9a21) and it seems to work so far.
But that does not address the other robustness issue that bertagaz has reported here.

#7 Updated by intrigeri 2018-09-18 16:23:52

  • Status changed from Confirmed to In Progress

Applied in changeset commit:a1d045bd167e47d620d6c2b22259bf6a946e9a21.

#8 Updated by intrigeri 2019-03-08 15:27:05

  • Status changed from In Progress to Confirmed

#9 Updated by intrigeri 2019-09-07 06:16:44

  • Assignee set to intrigeri

The recent failures here look like this:

03:46:37.768579404: executing Python as amnesia: node534 = node533.child('No Notifications', roleName='label')
03:46:41.843246621: execution complete
03:46:41.843435077: executing Python as amnesia: node535 = node533.child('No Notifications', roleName='label')
03:46:45.525478217: execution complete
03:46:45.568328359: [log]  TYPE "#ESC."
    And all notifications have disappeared                                                                                              # features/step_definitions/common_steps.rb:441
03:46:45.570811783: Sikuli: calling wait("GnomeApplicationsMenu.png")...
03:46:45.628754688: Remote shell: calling as amnesia: xdotool key Super
03:46:46.126956051: call returned: [0, "", ""]
03:46:46.127133834: Sikuli: calling wait("GnomeActivitiesOverview.png")...
03:47:12.730567115: Failed to find fuzzy candidate picture for GnomeActivitiesOverview.png
03:47:12.730779237: FindFailedHookFailure was raised, re-running the failing Sikuli method.
    When I delete the persistent partition                                                                                              # features/step_definitions/usb.rb:690
      FindFailed: can not find GnomeActivitiesOverview.png in S(0)[0,0 1024x768]
        Line 2171, in file Region.java
       (RuntimeError)

The video shows that we’ve successfully cleared all notifications but the Overview does not open.
We’ve pressed SUPER only 60ms after we’ve pressed ESC, which I think was too early: when the notifications menu is open, pressing SUPER does not open the Overview. I’ll add a sleep somewhere as a workaround.

#10 Updated by intrigeri 2019-09-07 06:25:00

  • Status changed from Confirmed to In Progress
  • Feature Branch set to test/17029+17027+17028+16931+force-all-tests

#11 Updated by intrigeri 2019-09-07 06:59:11

  • related to Feature #12652: Improve the 'I start ... via GNOME Activities Overview' step added

#12 Updated by intrigeri 2019-09-08 15:51:34

  • Status changed from In Progress to Needs Validation
  • Assignee deleted (intrigeri)
  • Target version set to Tails_4.0
  • Feature Branch changed from test/17029+17027+17028+16931+force-all-tests to https://salsa.debian.org/tails-team/tails/merge_requests/37#note_108671

#13 Updated by segfault 2019-09-12 16:14:15

  • Status changed from Needs Validation to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|e889519458da6235b299e4077a03d88a4fbdea7e.