action #169810: [qe-core] chrome & chromium 131 now interacts with the system keyring for password storage - openQA Tests (public) - openSUSE Project Management Tool

Actions

Copy link

action #169810

closed

[qe-core] chrome & chromium 131 now interacts with the system keyring for password storage

Added by dimstar 3 months ago. Updated 3 months ago.

Status:

Resolved

Priority:

Urgent

Assignee:

GraceWang

Category:

Bugs in existing tests

Target version:

Start date:

2024-11-13

Due date:

% Done:

100%

Estimated time:

Difficulty:

Tags:

bugbusters

Description

Observation¶

Seems since Chrome 131, the browser wants to access the system keyring - but as the SUT uses autologin, the keyring is not unlocked at the time chrome is launched

This produces a new password prompt, which is not covered by the test module

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_gnome@64bit fails in
chrome

Test suite description¶

Maintainer: QE Core, asmorodskyi. Extra tests which were designed to run on gnome

Reproducible¶

Fails since (at least) Build 20240919

Expected result¶

Last good: 20240918 (or more recent)

Further details¶

Always latest result in this scenario: latest

Actions

Copy link

Updated by dimstar 3 months ago

Subject changed from chrome 131 now interacts with the system keyring for password storage to chrome & chromium 131 now interacts with the system keyring for password storage
Priority changed from Normal to Urgent

This now also hits chromium tests

https://progress.opensuse.org/issues/169810

Actions

Copy link

Updated by szarate 3 months ago

Tags set to bugbusters
Subject changed from chrome & chromium 131 now interacts with the system keyring for password storage to [qe-core] chrome & chromium 131 now interacts with the system keyring for password storage

Actions

Copy link