https://bugzilla.suse.com/show_bug.cgi?id=1226204 https://bugzilla.suse.com/show_bug.cgi?id=1226204#c4 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #4 from Felix Miata <mrmazda@earthlink.net> --- 5 days later the exact details are no longer clearly remembered, while the nature of the installation abort prevented log collection. (In reply to Stefan Hundhammer from comment #2)
If you want a non-networked machine to start with
I don't, and apparently you don't understand what the actual problem is. To preface, not directly related to the bug, I normally don't use any iso. I fetch linux and initrd from oss/boot/x86_64/loader/ and load them with Grub. My network needs neither NM nor Wicked nor management, as systemd-network provides the tools required for my entirely static IP installations. And, installation does proceed as expected that way, due to fix for bug 1183886, unless.... The problem: some kind of failure ignores the overview deselection of both NM and Wicked when it is made /after/ detailed package selection has occurred, if during detailed package selection something gets selected, even accidentally but subsequently deselected, that is, or apparently is related to, NM or Wicked or some other network function or feature. Evidently the trigger is attempting to exit summary screen, seeing something disturbing in the consequent package resolver popup, or remembering haven forgotten to address something in detailed package selection, and returning to detailed package selection, one /or more/ times, for changes. Ultimately, NM and Wicked remain deselected, unwanted and unneeded, but to prevent them from being installed via taboo, prevents the installation process to continue from the summary screen once its use has been completed. Package selection on the summary screen notes in red that NM or Wicked must be selected to proceed. I suspect the underlying obstacle in such circumstance is the detailed package selection exit summary resolver being triggered multiple times. -- You are receiving this mail because: You are on the CC list for the bug.