Bug 1220889 - [YaST2][WSL] NVIDIA GPG keys popup appearance order changed
Summary: [YaST2][WSL] NVIDIA GPG keys popup appearance order changed
Status: RESOLVED INVALID
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP4
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact:
URL: https://openqa.suse.de/tests/13667422...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-04 14:43 UTC by Pablo Herranz Ramírez
Modified: 2024-03-06 16:16 UTC (History)
3 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Attachments
YaST2 logs (1.21 MB, application/gzip)
2024-03-04 14:43 UTC, Pablo Herranz Ramírez
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo Herranz Ramírez 2024-03-04 14:43:43 UTC
Created attachment 873203 [details]
YaST2 logs

In the WSL YaST2 installation, the NVIDIA popup for trusting the GPG keys appears in a different order depending on the version:

15-SP6: Registration screen --> Module selection --> SLEWE license screen --> Finish (No NVIDIA screen)
15-SP5: Registration screen --> Nvidia GPG popup --> Module selection --> SLEWE license screen
15-SP4: Registration screen --> Module selection --> SLEWE license screen --> Nvidia GPG popup
Comment 1 Pablo Herranz Ramírez 2024-03-04 14:49:51 UTC
Example jobs:
https://openqa.suse.de/tests/13667422
https://openqa.suse.de/tests/13667360
Comment 2 Lubos Kocman 2024-03-06 15:39:49 UTC
Team feel free to reassign the issue to libzypp if this is beyond yast. 
Ladislav and Josef has context from #discuss-wsl
Comment 3 Stefan Hundhammer 2024-03-06 16:16:21 UTC
Those pop-ups appear when they are needed; and that can be a different place in different contexts. This is not a bug; you simply need to be prepared for it.

I have no doubt that this is very annoying for OpenQA, but it's not a bug.

In those screenshots (which I have to puzzle apart on my own without any hint what I am looking for, NOT EVEN A SCREENSHOT NUMBER TO LOOK FOR!!) I see at one point an update repo being activated. Well, in that case, if there is a newer NVidia RPM, the NVidia package will demand you to agree to their EULA once more - they love to do that, and yes, it's annoying, but this is something to discuss with NVidia.

If an when there is an updated package that needs again their license confirmed is subject to change all the time. You need to be prepared for it. Again, this is not a bug.