Bug 130173 - Upgrade crashing after restart leaving unusable system
Summary: Upgrade crashing after restart leaving unusable system
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Alpha 2
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-22 23:42 UTC by Michael Stather
Modified: 2008-06-25 09:52 UTC (History)
0 users

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


Attachments
YaST2 log folder (1.02 MB, application/x-gzip)
2005-10-24 18:30 UTC, Michael Stather
Details
hwinfo output (199.86 KB, application/octet-stream)
2005-10-24 18:30 UTC, Michael Stather
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stather 2005-10-22 23:42:01 UTC
I tried to upgrade my system from Alpha1 to Aplha2. After the update of the
first CD was complete, the computer restarted. When it went into YaST2 again I
saw the animated cursor on a blank screen (as usual) then the X server
terminated, restarted with the "X" cursor and then terminated again. I got a
"Segmentation Fault in Wizard.ycp:372" error. Additional details were (not
everything but the most details I could write to a paper while it was on the
screen): .../yast2.call line 283: 141551 Speicherzugriffsfehler y2base ...
Then it continued to start up (I think it assumed setup ran properly) and
started the X server but hung while starting KDE. To make my system useable
again I had to "downgrade" to Alpha1 again.
Since I can´t install Alpha2 (and I want to tets it) I´d really like to help
debugging here, which logs should I post. I think as I ran the installer again
(to downgrade) the logs are in an archive or something?
Comment 1 Michael Radziej 2005-10-24 09:52:50 UTC
Can you please attach the output of hwinfo and the /var/log/YaST2 directory (as a tar file)? Please take a look at http://www.opensuse.org/Bug_Reporting_FAQ#YaST
if you have any questions about this.
Comment 2 Marcus Schaefer 2005-10-24 13:08:41 UTC
sorry this upgrade scenario is not supported between alpha versions.
If you will find that bug while upgrading from 10.0 to a beta or RC version
please reopen it again.
Comment 3 Michael Stather 2005-10-24 18:30:12 UTC
Even if this is amrked as "wontfix" I post the logs anyway.
I hope you won´t expect me to reinstall after each alpha version.
I test the alphas in a "real" environment with all my data and programs.
Comment 4 Michael Stather 2005-10-24 18:30:33 UTC
Created attachment 55256 [details]
YaST2 log folder
Comment 5 Michael Stather 2005-10-24 18:30:58 UTC
Created attachment 55257 [details]
hwinfo output
Comment 6 Michael Stather 2005-10-26 08:05:24 UTC
Do you think backing up my home dir and restoring it on the new alpha will work? Or can I use the "backup" feature of YaST between versions?
Comment 7 Marcus Schaefer 2005-10-26 08:14:19 UTC
I'd prefere rsync as backup solution. But please note bugzilla
is not a support mailing list :-) We are off topic now and I would
like to ask you to reopen this one if you encounter a bug while testing
the suggestion made in comment #2. Thanks
Comment 8 Stephan Kulow 2008-06-25 09:33:54 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 9 Stephan Kulow 2008-06-25 09:35:32 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 10 Marcus Schaefer 2008-06-25 09:39:58 UTC
it wasn't re-opened according to my last comment so this is not a bug
Comment 11 Stephan Kulow 2008-06-25 09:41:29 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 12 Stephan Kulow 2008-06-25 09:52:58 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(