Bug 1078815

Summary: Error when selecting Custom twice during User Interface selection
Product: [openSUSE] openSUSE Distribution Reporter: Wang <wb_jerry>
Component: InstallationAssignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: jreidinger
Version: Leap 15.0   
Target Milestone: ---   
Hardware: Macintosh   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Wang 2018-02-01 16:21:44 UTC 
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0
Build Identifier: 

I am testing Leap build 115.1 on Virtualbox Version 5.2.6 r120293 and my OS version is mac OS High Sierra Version 10.13.3. During the installation when I am asked to select User Interface, if I select 'Custom' and click next, then click back to the User Interface selection, then click next again, an error would occur saying "SetOverlay called when old overlay was not cleared"

Reproducible: Always

Steps to Reproduce:
1.Boot using build 115.1 iso
2.proceed to User Interface, click 'Custom' then 'next'
3.Make no change to the software selection, click 'back'
4.Now you are back to the User Interface, and the selection should still be 'Custom'. Click 'next' again and an error will pop up.
Actual Results:  
Error

Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.
Details: SetOverlay called when old overlay was not cleared
Caller: /mounts/mp_0001/usr/share/YaST2/modules/ProductFeature.rb:329: in 'SetOverlay'

Expected Results:  
Should see software selection page again.
Comment 1 Wang 2018-02-01 16:58:38 UTC 
Actually when you are back at the User Interface page, you can select other options like KDE or Gnome, and the error would still occur.
Comment 2 Josef Reidinger 2018-02-02 15:39:36 UTC 
We get it also in another bug report, so keep it in one only.

*** This bug has been marked as a duplicate of bug 1078961 ***