Project

General

Profile

action #40094

[functional][u] xscreensaver disabled in updates_packagekit_gpk.pm is back in x11 tests

Added by ggardet_arm almost 3 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Normal
Category:
Bugs in existing tests
Target version:
Start date:
2018-08-22
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

'xscreensaver-command -exit' done in tests/update/updates_packagekit_gpk.pm#L29 is lost (apparently) after a relogin (at least in LXDE): https://openqa.opensuse.org/tests/739615#step/midori/17

We should find a way to disable it for good.

Possible solutions are:
1) add 'xscreensaver-command -exit' also in tests/x11/user_gui_login.pm
2) disable it for good in tests/update/updates_packagekit_gpk.pm (mask a service, change the configuration, remove the package, ...)


Related issues

Related to openQA Tests - action #39827: [sle][functional][y] test fails in nis_client - gnome screen lock was not turned offResolved2018-08-16

Related to openQA Tests - action #40490: [qe-core][functional] Implement test for screensaver and disable it in other scenariosWorkable2018-08-31

History

#1 Updated by okurz almost 3 years ago

  • Subject changed from xscreensaver disabled in updates_packagekit_gpk.pm is back in x11 tests to [functional][u] xscreensaver disabled in updates_packagekit_gpk.pm is back in x11 tests
  • Category set to Bugs in existing tests
  • Target version set to Milestone 20

I guess the best solution is finally and after all make the screensaver check explicit, e.g. in consoletest_finish only detect anything graphical, locked or not, and in an explicit module detect the screensaver lock, unlock it once, disable it for good and then no further test module should care about a potentially locked screen

#2 Updated by okurz almost 3 years ago

  • Related to action #39827: [sle][functional][y] test fails in nis_client - gnome screen lock was not turned off added

#3 Updated by ggardet_arm almost 3 years ago

Not sure if consoletest_finish is the best place to do that, because we have graphical tests before consoletest_finish, e.g. updates_packagekit_gpk, keymap_or_locale.

Anyway, we must disable lock screen for good.

#4 Updated by okurz almost 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: lxde
https://openqa.opensuse.org/tests/758433

#5 Updated by okurz almost 3 years ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5808 disables screensaver on lxde already. I guess this should be made consistent for all DEs.

#6 Updated by ggardet_arm almost 3 years ago

I agree it should be made consistent across DEs, but this is not working properly yet, since screen is still locked on glxgears.
Maybe we should just use the gfx interface for all DEs, as done for KDE.

#7 Updated by ggardet_arm almost 3 years ago

The problem was it was disabled in system config file, but there was also a user config file. So, disable it there too.
MR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5828

#8 Updated by okurz over 2 years ago

  • Target version changed from Milestone 20 to future

#9 Updated by okurz over 2 years ago

  • Related to action #40490: [qe-core][functional] Implement test for screensaver and disable it in other scenarios added

#10 Updated by SLindoMansilla over 1 year ago

  • Status changed from New to Rejected
  • Assignee set to SLindoMansilla

Link already cleaned up.
I think this is already handled by ensure_unlocked_desktop

Also available in: Atom PDF