|
Bugzilla – Full Text Bug Listing |
| Summary: | When installation is finished - after reboot system wants to start installion again | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Holger Sickenberg <holgi> |
| Component: | Installation | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aj |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
YaST2.tgz
y2logs |
||
|
Description
Holger Sickenberg
2006-10-25 11:03:02 UTC
Created attachment 102549 [details]
YaST2.tgz
Just answer [No]. But this appears every time I reboot the system ... This is how the installation ends... 2006-10-25 12:41:34 <1> luna(4052) [agent-ppd] PPDdb.cc(setCheckMethod):1897 Setting PPD files checking to size only 2006-10-25 12:41:34 <1> luna(4052) [agent-ppd] PPDdb.cc(createdbThread):419 CreateDbThread started 2006-10-25 12:41:34 <1> luna(4052) [agent-ppd] PPDdb.cc(loadPrebuiltDatabase):1439 Database file parsed correctly by YCP parser 2006-10-25 12:41:34 <1> luna(4052) [agent-ppd] PPDdb.cc(loadPrebuiltDatabase):1670 Database contents is OK this doesn't appear to be correct... rather something like `abort` Miso? OK, Holger, remove the file /var/lib/YaST2/runme_at_boot I got a similar behaviour: - installation failed at network test - installation asked for root password [I left the system for ~5 minutes] -> I was presented with the kdm screen. The usual steps like user or hw configuration were omitted. After a reboot, I was asked if I wanted to start again. I did, the expected steps were all there, and the installation finished. On subsequent reboots, I was not asked again to restart the installation. I will attach my y2logs also. Created attachment 102560 [details]
y2logs
This is already fixed in #214265 Well, starting an installation again in case of previous failure is a new feature. YaST is started again, if the file /var/lib/YaST2/runme_at_boot exist. Rasmus, your y2log says: Removing /var/lib/YaST2/runme_at_boot Removing file /var/lib/YaST2/second_stage_failed Removing file /var/lib/YaST2/step and clients/installation_worker.ycp:528 Called YaST client returned: `next This means everything went OK for the second time Also this shows that the installation was somehow aborted: grep "=== installation" y2log 2006-10-25 09:11:27 <1> linux(4168) [YCP] clients/installation.ycp:34 === installation === 2006-10-25 11:44:08 <1> rumms(4176) [YCP] clients/installation.ycp:34 === installation === 2006-10-25 12:10:05 <1> rumms(4176) [YCP] clients/installation_worker.ycp:36 === installation === It should always show that with line 34 (starting) and line 36 (finishing), but for the first time, there was only the line 34. Ah, I see... according to comment #8: Bug 214265 - YAST2 printer module crashes rebuilding the driver database -- fixed in yast2-printer-2.14.4 ...and guess in which version is yast2-printer in Beta1? yast2-printer-2.14.3 Andreas: It seems that the printer module crashes the second stage installation, next time, the installation is restarted because it had crashed before. This will be very annoying for Beta1. *** This bug has been marked as a duplicate of bug 214265 *** |