https://bugzilla.novell.com/show_bug.cgi?id=292011#c9 --- Comment #9 from Matthew Fisher <flatrivercobol@comcast.net> 2007-07-27 11:01:40 MST --- (In reply to comment #8 from Ladislav Slezak) I'll leave this bug assigned to Thomas Fehr (fehr@novell.com), because I don't want to interrupt the workflow. However, I'd like to respond to the course of action selected by Ladislav Slezak (lslezak@novell.com).
The root password is not set because the initial installation was not completed (the GNOME installation failed). The password is configured after installing all selected packages.
Update updates only packages, it leaves the root password untouched, so the result is obvious...
That makes sense. Thank you.
So the "no password" problem is INVALID.
I see your point. No password is a symptom, not a cause. However, I don't see that the root problem is being addressed. The failure occurred due to htdig, which evidently is required for GNOME. But surely this isn't the only optional package which will ever cause an installation to fail. The real issue is a more general problem with the installer. I propose 3 alternative remedies: 1) The installer should prompt the user for a root password before installing any optional packages. 2) If this isn't feasible, the installer should automatically identify cases where openSUSE has been installed without prompting for a root password. In such cases, it should either a) prompt the user for a root password, or b) require a fresh install, and instruct the user to omit the optional package which caused the failure. 3) If this isn't feasible, the "no password" problem and the workaround should be listed as one of the most annoying bugs, or in some other place where it may be easily discovered. I'm not annoyed, but this is a fatal outcome which occurs with some frequency during openSUSE installations. Users should be advised that the workaround is to run a fresh install, in which they must omit the optional package which caused the failure. (It's not reasonable to expect users to intuit that a fresh install is required when an update is allowed.)
But it seems that there might be a problem in the partitioner (it could not partition the disk properly).
Thank you for addressing the partitioner problem. Should I open new a new ticket for the root cause of the "no password" problem? In my opinion the root cause is a design flaw in the installer, to which one of the remedies proposed above should be applied. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.