Bug 1221795

Summary: [Build 20240320] gnome_control_center accesses gnome keyring
Product: [openSUSE] openSUSE Tumbleweed Reporter: Dominique Leuenberger <dimstar>
Component: Live MediumAssignee: Dominique Leuenberger <dimstar>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: guillaume.gardet
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://openqa.opensuse.org/tests/4029116/modules/gnome_control_center/steps/10
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---

Description Dominique Leuenberger 2024-03-21 09:17:36 UTC
## Observation

Seems g-c-c now tries to access the keyring - which the user might not yet have accessed/setup 

openQA test in scenario opensuse-Tumbleweed-GNOME-Live-x86_64-gnome-live@USBboot_64-3G fails in
[gnome_control_center](https://openqa.opensuse.org/tests/4029116/modules/gnome_control_center/steps/10)

## Test suite description
Maintainer: dimstar@opensuse.org

Test for openSUSE GNOME Next Live-Media

EXCLUDE_MODULES is a workaround for https://bugzilla.opensuse.org/show_bug.cgi?id=1138401#c10 (except for opensuse_welcome, which is blacklisted on the GNOME live for space reasons)


## Reproducible

Fails since (at least) Build [20240320](https://openqa.opensuse.org/tests/4028701)


## Expected result

Last good: [20240319](https://openqa.opensuse.org/tests/4026100) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=GNOME-Live&machine=USBboot_64-3G&test=gnome-live&version=Tumbleweed)
Comment 2 Dominique Leuenberger 2024-03-21 10:28:10 UTC
more specifically: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2968
Comment 3 Dominique Leuenberger 2024-04-29 13:40:01 UTC
(In reply to Dominique Leuenberger from comment #2)
> more specifically:
> https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2968

Fixed in tW since Snapshot 0329- confirmed by openQA