Bug 402146

Summary: yast segfaults when choosing to run online update in second stage of install
Product: [openSUSE] openSUSE 11.0 Reporter: Wolfgang Rosenauer <wolfgang>
Component: YaST2Assignee: Forgotten User h13THG8RK1 <forgotten_h13THG8RK1>
Status: RESOLVED NORESPONSE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: forgotten_h13THG8RK1, jdouglas
Version: Final   
Target Milestone: ---   
Hardware: i586   
OS: openSUSE 11.0   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs

Description Wolfgang Rosenauer 2008-06-20 14:21:03 UTC
yast segfaults when choosing to run online update in second stage of install

That happens reproducible for me:
1. start installation (non-automatic) and just choose Gnome
2. let it do the install, set up the network, configure online update
3. choose to run online update now

YaST2 segfaults and proceeds starting up the system w/o doing any more config stuff leaving the system in an almost unusable state (no local user, no more config).
Because it just proceeds and starts up X I couldn't gather the actual console output yet but I can see that it's a segmentation fault trying to run inst_you (I guess).
(As I've chosen Gnome this is actually YaST2 Gtk)
Comment 1 Wolfgang Rosenauer 2008-06-20 14:27:10 UTC
Installation performed from DVD5
Comment 2 Cyril Hrubis 2008-06-20 16:29:03 UTC
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 3 Wolfgang Rosenauer 2008-06-20 19:04:04 UTC
Created attachment 223480 [details]
y2logs
Comment 4 Jiri Srain 2008-06-23 08:30:37 UTC
Yes, it crashes inside the GTK back-end (see backtrace in the log).

Ricardo, could you, please, have a look?
Comment 5 Forgotten User h13THG8RK1 2008-06-23 17:54:11 UTC
I'm guessing that the installation screen second-stage thing still appears at startup? If so, you could try to remove yast2-gtk and install yast2-qt -- it will automatically pick it up -- to see if you can reproduce it with -qt. (you can use yast2-gtk package management to remove itself since the thing will be all in memory.)

If the second-stage doesn't appear anymore, there's some file you can edit to make it so. And it's also possible to run the thing manually. Jiri, you probably know the details, right? Can you tell Wolfgang here how to make the second-stage install appear?

Thanks.
Comment 6 Forgotten User h13THG8RK1 2008-06-23 17:57:51 UTC
Wait, Jiri points out that the logs pin out the point of the crash at the yast2-gtk code. So we will want Wolfgang to compile it by hand with some debugging on. I'll later look into it and give you instructions...

Meanwhile, Jiri please tell us how to re-run the second stage.
Comment 7 Jiri Srain 2008-06-24 09:42:34 UTC
touch /var/lib/YaST2/runme_at_boot

does make second stage run again after reboot.
Comment 8 Forgotten User h13THG8RK1 2008-06-24 18:47:40 UTC
Wolfgang, could you try out, to see if you can reproduce the bug:
  gdb --args /usr/lib/YaST2/startup/YaST2.Second-Stage
  (you may need to press Enter a couple of times.)

If you can reproduce it, and crash it, then type "backtrace" and post the output here.

Thanks!
Comment 9 Forgotten User h13THG8RK1 2008-06-24 19:38:01 UTC
Oh, I forgot to mention you need to type "run" on the gdb shell to actually execute the thing... So:
  gdb --args /usr/lib/YaST2/startup/YaST2.Second-Stage
  run
  (you may need to press Enter a couple of times.)
Comment 10 Forgotten User h13THG8RK1 2008-06-24 19:43:26 UTC
Actually, gdb doesn't like script. Run the following instead:
  gdb --args /usr/lib/YaST2/bin/y2base installation '("continue")' gtk
  run
  (you may need to press Enter a couple of times.)
  ...
  (crash)
  backtrace

Thanks!
Comment 11 Jason Douglas 2008-07-11 18:13:04 UTC
I'm seeing this crash as well, so I thought I'd provide the needed information.  However, when I tried to run gdb as described in #10, the installation program skipped the online update portion of the install.  When I tried to go back and run it, the network was down.  The bottom line is that I couldn't get yast to run the code that segfaulted.  Was I supposed to run something before executing the steps in comment #10?  Any suggestions would be helpful.
Comment 12 Forgotten User h13THG8RK1 2008-07-31 02:06:10 UTC
Jason, yast is huge including a platform with its own language and then the various tools are programmed for it. I don't have much clue how these work.
Wolf, if you can run this, that would be great because actually doing a gdb on it will tell us the exact line. If you can't get that working, we could also try updating to yast2-gtk so I'd put some extra debugging there...
Comment 13 Forgotten User h13THG8RK1 2008-07-31 23:43:13 UTC
Well, I guess we'll have to see if someone else comes up with this problem.