Project

General

Profile

Actions

action #70717

open

[qe-core][kde] Password not typed in KDE lockscreen

Added by ggardet_arm over 3 years ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-08-31
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-upgrade_Leap_15.2_kde@aarch64 fails in
consoletest_finish

The problem is the password is not typed in KDE lockscreen.

Test suite description

Upgrade scenario from Leap 15.2 with kde installed.

Reproducible

Fails since (at least) Build 20200820

Expected result

Last good: 20200807 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by ggardet_arm over 3 years ago

In addition to consoletest_finish, it also happen in user_gui_login: https://openqa.opensuse.org/tests/1377998#step/user_gui_login/9

Actions #2

Updated by SLindoMansilla over 3 years ago

  • Subject changed from Password not typed in KDE lockscreen to [kde] Password not typed in KDE lockscreen
Actions #3

Updated by okurz over 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: kde@USBboot_aarch64
https://openqa.opensuse.org/tests/1399992

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #4

Updated by okurz over 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: kde
https://openqa.opensuse.org/tests/1420540

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #5

Updated by okurz over 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: kde
https://openqa.opensuse.org/tests/1442868

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #6

Updated by okurz over 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: kde@USBboot_aarch64
https://openqa.opensuse.org/tests/1457386

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #7

Updated by okurz over 2 years ago

I came to this ticket due to periodically reviewing tickets as described on https://progress.opensuse.org/projects/openqatests/wiki#How-we-work-on-tickets

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives

First reminder: Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).

Actions #8

Updated by slo-gin over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #9

Updated by okurz over 1 year ago

  • Subject changed from [kde] Password not typed in KDE lockscreen to [qe-core][kde] Password not typed in KDE lockscreen
Actions #10

Updated by slo-gin about 2 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF