|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation update from 10.0 RC1 to Final Release hangs 15 minutes and fails with a blue screen | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Ulrich Lange <email> |
| Component: | Update Problems | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Can you please attach the /var/log/YaST2 directory (as a tar file)? I looked into all logfiles. There were no entrys about this installation. It looked a bit like a problem with reading CDROM, but the drive was ok. Then look at console 4 (ctrl-alt-f4) where kernel messages are shown. Or switch to a shell at console 2 and run 'dmesg' Sorry Klaus, I wrote that this bug was not reproducible. So this advice makes not sense at the moment. My point was more that the system reacts after approx. 15 minutes and not after 1 minute by example and than with a pur message (see above). I see your point, but without logs it's not even possible to tell what component is causing this. Also, I haven't seen such a bug report before. Thus, I close it as worksforme, but if it happens again, please reopen this bug. |
Update installation hangs in screen "Package installation". Only the running clock is shown. Abort and Help Button is shown as active. Back and Next Button is shown as inactive. Help Button is changeable to Step. Abort Button shows no reaction. After approx. 15 minutes a blue screen was shown with: >>> Linuc rc v 1.9.16 (Kernel 2.6.13-15-default) <<< and an error message in a red window with: An error occurred during the installation. Unfortunately, this bug was not reproducible. But this error handling is very pur and look like MS. We should expect an error message after in maximum 1 minute with a more detailed message. A similar bug was reported under #104038 and marked as fixed.