Red Hat Bugzilla – Bug 1020672
[Firstboot] Invalid/Not providing credentials in the register screens of first boot send the main firstboot screen to background/minimised
Last modified: 2014-11-03 10:42:13 EST
Description of problem:
Observed that when no/wrong user details were given in the firstboot subscription register screen, firstboot screen was send to background/minimised
Version-Release number of selected component (if applicable):
server type: This system is currently not registered.
subscription management server: 0.8.29-1
Steps to Reproduce:
2.move to subscription register screen
3.click forward without entering the credentials --(A)
4.Issue wrong credentials and click next (B)
Observed that during both the cases (A) & (B) when the error message screen pops up the main First boot screen was getting minimised or send to background and after clicking "Ok" on the msg window the firstboot screen didnt come up
The error screen should display on the main first boot screen and after clicking "Ok" on the error message screen the control should go back to first boot screen
Need to verify but I suspect this is just how firstboot behaves when an error is thrown and you're running it manually *after* logging into the system. (note that this is not how firstboot is normally meant to be used, only something we do for dev/QE testing)
I have seen this behaviour for popups after hardware profile reporting screens in firstboot, I think it's just an issue with how firstboot behaves if you're already logged in.
Need to test this but suspect this is a close wontfix or cantfix.
Moving bugs from 7.0 to 7.1
Closing as firstboot is largely unmaintained now, and we are only considering critical fixes.
Will be addressed for 7.2 by the planned port to new anaconda installer modules. More details in comment #1.