Bug 121858 - Installation update from 10.0 RC1 to Final Release hangs 15 minutes and fails with a blue screen
Summary: Installation update from 10.0 RC1 to Final Release hangs 15 minutes and fails...
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Final
Hardware: Other All
: P5 - None : Major
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-08 22:07 UTC by Ulrich Lange
Modified: 2005-10-10 17:31 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Lange 2005-10-08 22:07:10 UTC
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.
Comment 1 Michael Radziej 2005-10-09 16:40:33 UTC
Can you please attach the /var/log/YaST2 directory (as a tar file)?
Comment 2 Ulrich Lange 2005-10-09 20:04:41 UTC
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.
Comment 3 Klaus Kämpf 2005-10-10 06:43:11 UTC
Then look at console 4 (ctrl-alt-f4) where kernel messages are shown. Or 
switch to a shell at console 2 and run 'dmesg' 
Comment 4 Ulrich Lange 2005-10-10 09:39:10 UTC
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).
Comment 5 Michael Radziej 2005-10-10 17:31:37 UTC
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.