https://bugzilla.novell.com/show_bug.cgi?id=292011 Matthew Fisher <flatrivercobol@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Got to linux login, without |Install procedure does not prompt user for root |having created any accounts |password. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=292011#c3 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |flatrivercobol@comcast.net --- Comment #3 from Cyril Hrubis <chrubis@novell.com> 2007-07-17 06:10:42 MST --- If it's possible please attach y2logs from the failed installation. http://en.opensuse.org/Bugs/YaST Thanks! -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=292011#c5 Matthew Fisher <flatrivercobol@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |flatrivercobol@comcast.net Status|NEEDINFO |NEW Info Provider|flatrivercobol@comcast.net | --- Comment #5 from Matthew Fisher <flatrivercobol@comcast.net> 2007-07-23 19:13:31 MST --- I'm stumped. The logs don't exist at the moment, because my workaround involves deleting the Linux partitions and running a more minimal install. It's no problem to delete the Linux partitions again, and reproduce the problematic installation. The problem is, how would I retrieve the log files? Recall that openSUSE installs and boots, but I don't have any account credentials. So the logs must exist, but how would I get to them? I thought, no problem, I'll just mount the Linux partition from Windows. But I haven't yet found a utility which will run under the 32-bit version of Windows Vista, and can mount EST3 partitions. If I understand correctly, EST2FSD doesn't support 32-bit Vista. I tried it anyway, but couldn't manage to do anything more than changing drive letters in the EST2FSD GUI. Nothing changes in Windows Explorer, so I can't actually get to the Linux partitions. Any ideas? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=292011#c7 --- Comment #7 from Matthew Fisher <flatrivercobol@comcast.net> 2007-07-23 23:20:14 MST --- Created an attachment (id=152554) --> (https://bugzilla.novell.com/attachment.cgi?id=152554) y2log archive The y2logs are attached. A red error dialog occurred twice during the installation. If I understand correctly, this causes logs to be restarted. As supporting documentation, here's a description of what occurred during the install. In Windows, I deleted the Linux partitions. I then booted from openSUSE 10.2 CD1, and selected Installation. Language: English (US) > Next. Media Check: (skipped) > Next. License Agreement: Yes > Next. Installation Mode: New Installation > Next. Clock and Time Zone: USA, Central > Next. Desktop Selection: GNOME > Next. Installation Settings: Accept. Confirm Installation: Install. Error: Failure occurred during the following action: Setting type of partition /dev/sda5 to 82. System error code was: -1012. Clicked OK, and a red error dialog appeared: "An error occured during the installation". OK. Main Menu: Start Installation or System. OK. Start Installation or Update: OK. Choose the Source Medium: CD-ROM. OK. Loading installation system.... We're back at the Language menu. Provided same responses as before. Responded OK to a confirm driver activation dialog. Warning: "The partitioning on disk /dev/sda is not readable by the partitioning tool parted, which is used to change the partition table. You can use the partitions on disk /dev/sda as they are. You can format them and assign mount points to them, but you cannot add, edit, resize, or remove partitions from that disk with this tool." OK. Installation Mode: New Installation > Next. Desktop Selection: GNOME > Next. Installation Seetings: Partitioning: "No automatic proposal possible. Specify mount points manually in the Partioner dialog." Change > Partitioning. Preparing Hard Disk: Custom Partitioning > Next. Expert Partitioner. Hmm. This looks like I could wipe out Windows if I make a mistake. So.... Abort > Reboot. Installation, etc., Accept, Install. Insert CD2. Error: "Package htdig was not found on the medium." Ignore. Red error dialog: "An error occurred during the installation." OK. Start Installation, etc., Update > Next, etc. Installation Settings > Packages > Search: htdig. Deselect htdig. Accept, etc., Start Update. Installation continues. Prompted to write boot loader record (or something like that) to a floppy. There's no floppy drive on this PC. Clicked OK. Got an error. Forget how I responded. Eventually was able to select GRUB, and asked the installer to propose settings. Accepted them. Install ran to completion. Initial boot occurs. Omitted the internet connection test. Everything seems OK. Linux login prompt appears. I was never prompted to provide a root password, or to create any account. So I'm effectively locked out of this otherwise successful installation. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=292011 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.novell| |.com | Severity|Blocker |Critical -- 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.

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.