|
Bugzilla – Full Text Bug Listing |
| Summary: | first boot after installation takes long an than all configuration steps are skipped | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Hendrik Woltersdorf <hendrikw> |
| Component: | Installation | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | fcrozat |
| Version: | 13.1 Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | content of /var/log after the first reboot | ||
I found a workaround for the missing configuration part. After logging in as root, I started: /usr/lib/YaST2/startup/YaST2.Second-Stage manually. RC1: Bug is still there, used the workaround described above again. In the log I see entries of the automatic start of this unit, but it doesn't come up: ... 2013-02-07T20:49:20.541627+01:00 linux systemd[1]: Stopped SuSEfirewall2 phase 2. 2013-02-07T20:49:23.765626+01:00 linux systemd[1]: Started Getty on tty5. 2013-02-07T20:49:25.552531+01:00 linux systemd[1]: Started YaST2 Second Stage. 2013-02-07T20:49:25.553487+01:00 linux systemd[1]: Started YaST2 Firstboot. 2013-02-07T20:49:25.554072+01:00 linux systemd[1]: Starting Network Manager... 2013-02-07T20:49:25.600163+01:00 linux systemd[1]: Starting LSB: X Display Manager... 2013-02-07T20:49:25.617525+01:00 linux systemd[1]: Starting Getty on tty1... 2013-02-07T20:49:25.637896+01:00 linux systemd[1]: Started Getty on tty1. 2013-02-07T20:49:25.637925+01:00 linux systemd[1]: Starting Forward Password Requests to Wall... 2013-02-07T20:49:25.650251+01:00 linux systemd[1]: Starting Login Prompts. ... There are some error messages in this log. I don't know, if they are in any way related to this issue, but here they are: 2013-02-07T20:49:41.982605+01:00 linux systemd[1]: Startup finished in 5s 651ms 490us (kernel) + 51s 222ms 659us (userspace) = 56s 874ms 149us. 2013-02-07T20:49:51.119327+01:00 linux kdm: :0[1139]: gkr-pam: error looking up user information 2013-02-07T20:49:51.120989+01:00 linux kdm: :0[1139]: pam_unix(xdm:auth): check pass; user unknown 2013-02-07T20:49:51.122117+01:00 linux kdm: :0[1139]: pam_unix(xdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= Jiri, could you please investigate what's going wrong while installation? Frederic, was this already solved somewhere? Seems like boot services fail to start YaST... there was bnc#800365 but it is fixed now. So probably duplicate *** This bug has been marked as a duplicate of bug 800365 *** |
Created attachment 520968 [details] content of /var/log after the first reboot User-Agent: Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0 This misbehavior startet with os12.3M2 and is in Beta1 too. I start the installation by booting from DVD (32Bit, openSUSE-DVD-Build0348-i586.iso). All information is gathered, all packages get installed boot configuration is written, etc. Than the system reboots. This boot takes a long time and then instead of starting the second part of the installation (lots of configuration) the normal login window is displayed (KDE). I can login only as root because the user, that should have been created by the installation does not exist. Now I have to do all the configuration steps manually: - create a user - configure network - create all software repositories (beside the installation DVD) - configure sound ... Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: The second part of the installation does not start after the first reboot and all these configuration steps have to be done manually. Expected Results: After the first reboot the system configuration should start. The attached file contains all files from /var/log from some time after the first reboot. So it should (hopefully) contain helpful error messages.