Project

General

Profile

Actions

action #132191

closed

[desktop] After SDDM 0.20, kde-wayland switches test to wrong VT on shutdown

Added by favogt over 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-06-30
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Somehow the shutdown test ends up switching to tty5 instead of tty2.
I wonder how this worked previously at all...

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-kde-wayland@64bit_virtio fails in
shutdown

Test suite description

Basic KDE installation, but switches to a Wayland session on login. Needs Virtio (or similiar) GPU.

Reproducible

Fails since (at least) Build 20230629

Expected result

Last good: 20230628 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by maritawerner over 1 year ago

@zcjia is that for your team to have a look?

Actions #2

Updated by openqa_review over 1 year 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-wayland@64bit_virtio
https://openqa.opensuse.org/tests/3430146#step/shutdown/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #3

Updated by maritawerner over 1 year ago

  • Subject changed from After SDDM 0.20, kde-wayland switches test to wrong VT on shutdown to [desktop] After SDDM 0.20, kde-wayland switches test to wrong VT on shutdown
Actions #4

Updated by openqa_review over 1 year 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-wayland@64bit_virtio
https://openqa.opensuse.org/tests/3500593#step/shutdown/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 36 days if nothing changes in this ticket.

Actions #5

Updated by openqa_review over 1 year 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-wayland@64bit_virtio
https://openqa.opensuse.org/tests/3579965#step/shutdown/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 72 days if nothing changes in this ticket.

Actions #6

Updated by openqa_review about 1 year 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-wayland@64bit_virtio
https://openqa.opensuse.org/tests/3762961#step/shutdown/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 144 days if nothing changes in this ticket.

Actions #7

Updated by favogt 11 months ago

  • Status changed from New to Resolved
  • Assignee set to favogt
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF