Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Quoting Denis Laxalde (dlaxa...@gmail.com): I would then say that this bug is not reproducible and its severity In such case, it's perfectly OK for you to close it (send a mail - bugnr-d...@bugs.d.o.sorry for being pedantic if you lready knew this). may be downgraded. The partition formatting debate is probably another issue. If there's another issue, either clone the bug and try reassigning it to the relevant d-i component. Also, at this moment of the release, feel free to draw attention from D-I release management by pointing blocker issues. Many many many thanks for your will to help in triaging. We desperately need that! signature.asc Description: Digital signature
Processed: Re: Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Processing commands for cont...@bugs.debian.org: tags 600320 unreproducible Bug #600320 [installation-reports] Installation: set password for root; did not create a user; could not login after 1st reboot. Added tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 600320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
tags 600320 unreproducible thanks On Tue, 23 Nov 2010 06:55:05 +0100, Christian PERRIER wrote: In such case, it's perfectly OK for you to close it (send a mail - bugnr-d...@bugs.d.o.sorry for being pedantic if you lready knew this). Done. If there's another issue, either clone the bug and try reassigning it to the relevant d-i component. Since it is not clear whether or not there is another issue, I'll let the original reporter report back eventually. Cheers, Denis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Hello, I'm trying to help a bit on triaging installation reports. Here, the main problem (as per the bug title and part of the report) seems to be (quoting John Hunter [2010-10-16]): I set up the root password but declined to create any [more] users. The install apparently finished OK and then I rebooted. Upon reboot, the system would not let me log in as root so that I could not manually set up /etc/password, /etc/shadow, /etc/group and /etc/sudoers. So, starting from that, I tried to reproduce this by doing a fresh (KVM) installation. I set a root password but did not create any regular user. The installation completed normally (just had to go back twice in the installation procedure to be able to skip the user creation step) and, upon reboot, I actually had no problem logging-in as root. I would then say that this bug is not reproducible and its severity may be downgraded. The partition formatting debate is probably another issue. Hope this helps... Denis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Quoting John Hunter (jmd...@btinternet.com): Package: installation-reports Version: 2.42 Severity: serious Tags: d-i Justification: Unknown Hello, thanks for your report... I was installing squeeze over an old version of Ubuntu which had users already set up in /home. I set up the root password but declined to create any [more] users. The install apparently finished OK and then I rebooted. Upon reboot, the system would not let me log in as root so that I could not manually set up /etc/password, /etc/shadow, /etc/group and /etc/sudoers. I then had to resort to using the CD in recovery mode to set up the users. If the setup script has not created a user then root should be allowed to log in; otherwise one's laptop is as useful as a bag of slates. I would call myself experienced; I am a retired comp-sci academic with *nix experience going back to System VII. I have seen install glitches in my time, but none as stupid as this. In all these years of experience, have you ever learned about sending possible useful information? ;-) For instance, with such a problem, sending the system's /etc/shadow and /etc/passwd would have been useful. The same stands for relevant log files, such as /var/log/auth.log. Additionnally, having log files from /var/log/installer could help (but, admittedly, this you couldn't guess). As is, our only chance to examine your bug is by trying to reproduce it. In passing, I should mention that on the 6th October, I tried to install squeeze using the network install image (191MB). That got as far as installing a bootstrap system then did not seem to have a script or any instructions to load anything more: thus resulting in another bag of slates. Was that ever tested? Daily builds are daily builds: they're built every day. Do you imagine that, in Debian factories, there is a full row of monkeys whose job is testing each and every bit produced in the project? So, no, daily builds are not testing systematically...and sometimes they fail. This is how development works, I'm afraid: the best testers are our users... signature.asc Description: Digital signature
Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Quoting Otavio Salvador (ota...@ossystems.com.br): Hello John, On Fri, Oct 15, 2010 at 9:06 PM, John Hunter jmd...@btinternet.com wrote: I was installing squeeze over an old version of Ubuntu which had users already set up in /home. I set up the root password but declined to create any [more] users. The install apparently finished OK and then I rebooted. Upon reboot, the system would not let me log in as root so that I could not manually set up /etc/password, /etc/shadow, /etc/group and /etc/sudoers. I then had to resort to using the CD in recovery mode to set up the users. From your description it looks like you did not formated the partition of data. Debian Installer cannot be installed (and it is not designed to be used in this case) to install over an existent system. In case you have a /home in a separated partition it can be reused but the system _need_ to be installed into a fresh partition. Hmmm, still. John explained that he specifically did not create any user, so I fail to see how re-using the /home partition would create a problem: the installer should then not write there, should it? His use case is a fairly valid use case. signature.asc Description: Digital signature
Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Hello, On Sat, Oct 16, 2010 at 3:17 AM, Christian PERRIER bubu...@debian.org wrote: Quoting Otavio Salvador (ota...@ossystems.com.br): Hmmm, still. John explained that he specifically did not create any user, so I fail to see how re-using the /home partition would create a problem: the installer should then not write there, should it? The problem is not about reusing /home but about reusing / that has /home on it. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Quoting Otavio Salvador (ota...@ossystems.com.br): Hello, On Sat, Oct 16, 2010 at 3:17 AM, Christian PERRIER bubu...@debian.org wrote: Quoting Otavio Salvador (ota...@ossystems.com.br): Hmmm, still. John explained that he specifically did not create any user, so I fail to see how re-using the /home partition would create a problem: the installer should then not write there, should it? The problem is not about reusing /home but about reusing / that has /home on it. The original bug report did not make it clear if only /home was re-used or also /. Apparently, there's a separate /home partition. signature.asc Description: Digital signature
Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Package: installation-reports Version: 2.42 Severity: serious Tags: d-i Justification: Unknown I was installing squeeze over an old version of Ubuntu which had users already set up in /home. I set up the root password but declined to create any [more] users. The install apparently finished OK and then I rebooted. Upon reboot, the system would not let me log in as root so that I could not manually set up /etc/password, /etc/shadow, /etc/group and /etc/sudoers. I then had to resort to using the CD in recovery mode to set up the users. If the setup script has not created a user then root should be allowed to log in; otherwise one's laptop is as useful as a bag of slates. I would call myself experienced; I am a retired comp-sci academic with *nix experience going back to System VII. I have seen install glitches in my time, but none as stupid as this. In passing, I should mention that on the 6th October, I tried to install squeeze using the network install image (191MB). That got as far as installing a bootstrap system then did not seem to have a script or any instructions to load anything more: thus resulting in another bag of slates. Was that ever tested? -- Package-specific info: Boot method: CD Image version: Disc 1 (04-oct-2010) Date: Date and time of the install Machine: Gateway Laptop Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20100912 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux archimedes 2.6.32-5-486 #1 Thu Aug 12 12:59:56 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 04) lspci -knn: Subsystem: Gateway 2000 Device [107b:0365] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) lspci -knn: Subsystem: Gateway 2000 Device [107b:0365] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 04) lspci -knn: Subsystem: Gateway 2000 Device [107b:0365] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04) lspci -knn: Subsystem: Gateway 2000 Device [107b:0365] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04) lspci -knn: Subsystem: Gateway 2000 Device [107b:0365] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 04) lspci -knn: Subsystem: Gateway 2000 Device [107b:0365] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 04) lspci -knn: Subsystem: Gateway 2000 Device [107b:0365] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 04) lspci -knn: Subsystem: Gateway 2000 Device [107b:0365] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d4) lspci -knn: 00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio
Bug#600320: Installation: set password for root; did not create a user; could not login after 1st reboot.
Hello John, On Fri, Oct 15, 2010 at 9:06 PM, John Hunter jmd...@btinternet.com wrote: I was installing squeeze over an old version of Ubuntu which had users already set up in /home. I set up the root password but declined to create any [more] users. The install apparently finished OK and then I rebooted. Upon reboot, the system would not let me log in as root so that I could not manually set up /etc/password, /etc/shadow, /etc/group and /etc/sudoers. I then had to resort to using the CD in recovery mode to set up the users. From your description it looks like you did not formated the partition of data. Debian Installer cannot be installed (and it is not designed to be used in this case) to install over an existent system. In case you have a /home in a separated partition it can be reused but the system _need_ to be installed into a fresh partition. If the setup script has not created a user then root should be allowed to log in; otherwise one's laptop is as useful as a bag of slates. See my description above. If it is not the case, please describe your use case more extensively. I would call myself experienced; I am a retired comp-sci academic with *nix experience going back to System VII. I have seen install glitches in my time, but none as stupid as this. I won't comment on this. In passing, I should mention that on the 6th October, I tried to install squeeze using the network install image (191MB). That got as far as installing a bootstrap system then did not seem to have a script or any instructions to load anything more: thus resulting in another bag of slates. Was that ever tested? Without the URL I can't know which version you've used. I must remind you that Squeeze is still in development and you being an experienced user you must know that during this process we can end up breaking the system sometimes. If you wish a stable system, use stable releases. For Squeeze Installer, alpha1 is the last release and beta1 is being prepared so we're proud of receiving feedback from users (be it positive or failure reports) but sarcasm is not going to help in fixing the bugs you found (or think to have found). Cheers, -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
